On Thu, Sep 17, 2009 at 12:31 PM, Hannu Krosing <ha...@2ndquadrant.com> wrote: >> Exactly. The application is typically going to throw a "concurrent >> update" type of error when this happens, and we don't want magic >> background operations to cause that. > > Would'nt current VACUUM FULL or CLUSTER cause much more grief in this > situation ?
No. They take an exclusive lock on the table, so this situation can't occur in those cases, which was Tom's point. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
