On Mon, Oct 6, 2014 at 10:59 AM, Andres Freund <and...@2ndquadrant.com> wrote: > On 2014-10-06 10:46:09 -0400, Robert Haas wrote: >> This seems messy, though. Can't the deferred trigger queue become >> non-empty at pretty much any point in time? At exactly what point are >> we making this decision, and how do we know the correct answer can't >> change after that point? > > What we've been talking about is doing this during executor startup. And > at that point we really don't care about new entries in the queue during > query execution - we can't see them anyway.
Ah, OK. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
