That is quite useful feature to implement smth. like message queues based on database and so on. Now there is possibility to jump over luck of such feature in Postgres using current advisory lock implementation (pg_try_advisory_xact_lock to determine if somebody already acquired log on particular row). So Im not sure this is an urgent matter.
Best regards, Ilya On Mon, Jan 16, 2012 at 6:33 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > It sounds to me like "silently give the wrong answers". Are you sure > there are not better, more deterministic ways to solve your problem? > > (Or in other words: the fact that Oracle has it isn't enough to persuade > me it's a good idea.) > > regards, tom lane > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
