Re: ORDER BY random() LIMIT 1 slowness - Mailing list pgsql-general

From scott.marlowe
Subject Re: ORDER BY random() LIMIT 1 slowness
Date
Msg-id Pine.LNX.4.33.0212181258290.3807-100000@css120.ihs.com
Whole thread Raw
In response to Re: ORDER BY random() LIMIT 1 slowness  (Jean-Luc Lachance <jllachan@nsd.ca>)
List pgsql-general
On Wed, 18 Dec 2002, Jean-Luc Lachance wrote:

> Alvara,
>
> But instead of returning an error, currval() should return last_value if
> nextval() was not called (with all the caveat of couse).  I think it
> would be more usefull that way.

no, that would be like walking around with a gun pointed at your foot, to
quote Tom Lane.

See my post on transactions and such. Remember that everything in
Postgresql is designed to make transactions safe.  currval working without
a nextval or setval before it is dangerous in the exterme to transactions.


pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: Measuring CPU time use? (Another stupid question)
Next
From: Jessica Blank
Date:
Subject: Re: Measuring CPU time use? (Another stupid question)