* Florian Pflug: > On 16.12.09 16:40 , Kevin Grittner wrote: >> Nicolas Barbier<nicolas.barb...@gmail.com> wrote: >> >>> I am not sure whether the serialization failures that it may cause >>> are dependent on the plan used. >> >> They are. > > But so are failures due to deadlocks even today, no?
They are detected. In this context, "serialization failure" means that PostgreSQL generates a history which lacks one-copy serializability, without reporting any errors. (In the general case, the unique constraint violation which bugs me personally is a different beast and does result in an error.) -- Florian Weimer <fwei...@bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
