Re: Hmm, nodeUnique doesn't really support backwards scan too well
От | Simon Riggs |
---|---|
Тема | Re: Hmm, nodeUnique doesn't really support backwards scan too well |
Дата | |
Msg-id | 1217996049.4549.126.camel@ebony.2ndQuadrant обсуждение исходный текст |
Ответ на | Re: Hmm, nodeUnique doesn't really support backwards scan too well ("Jaime Casanova" <jcasanov@systemguards.com.ec>) |
Список | pgsql-bugs |
On Tue, 2008-08-05 at 18:00 -0500, Jaime Casanova wrote: > On 8/5/08, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Simon Riggs <simon@2ndquadrant.com> writes: > > > I've never seen anyone scan backwards like this at all in practical use. > > > > > I knew it was possible, but never seen it done. > > > > > It seems entirely probable nobody else has either. It's a PostgreSQL > > > extension, so people arriving from outside don't even know it exists, > > > > Say again? Both the SCROLL option to DECLARE CURSOR and FETCH PRIOR are > > straight out of the SQL92 spec. Yep. I was talking about FETCH BACKWARDS n | ALL though forgot that this is the same thing as FETCH PRIOR. But even use of FETCH PRIOR is fairly rare, so IMHO your proposal is still safe. > i think Simon is talking about DISTINCT ON No, don't confuse things! That is rare also, but I know of various places that is used. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support
В списке pgsql-bugs по дате отправления: