On 2014-09-28 10:41:56 -0400, Tom Lane wrote: > David Rowley <dgrowle...@gmail.com> writes: > > Please correct anything that sounds wrong here, but my understanding is > > that we'll always plan a query right before we execute it, with the > > exception of PREPARE statements where PostgreSQL will cache the query plan > > when the prepare statement is first executed. > > If this optimization only works in that scenario, it's dead in the water, > because that assumption is unsupportable. The planner does not in general > use the same query snapshot as the executor, so even in an immediate- > execution workflow there could have been data changes (caused by other > transactions) between planning and execution.
I don't think the effects of other queries are the problem here. The effect of other backend's deferred FK checks shouldn't matter for other backends for normal query purposes. It's the planning backend that might have deferred checks and thus temporarily violated foreign keys. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
