On Mon, 2004-10-18 at 13:12 +1000, Michael Kraus wrote:
> No, this definetly opens up race conditions and lots of rollbacks and
> reprocessing.
> 
> Eg (in pseudocode).
> 
> id = execute("SELECT MAX(id) FROM tablename") + 1;
> ...
> result = execute("INSERT INTO tablename VALUE(id, ....)");
> if (!result) { rollback(); repeat(); }
> ----
> 
> Either that or it would cause the database performance to slow down
> whilst it holds a that table. Better just to have another unique
> identifier in my reckoning.

Have you profiled the performance of nextseq() in postgresql ? Or are
you just speculating?

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to