On Sun, Dec 21, 2014 at 6:56 AM, Peter Geoghegan <p...@heroku.com> wrote: > On Thu, Dec 18, 2014 at 9:31 AM, Peter Geoghegan <p...@heroku.com> wrote: >>> So I think there needs to be some kind of logic to de-recognize the table >>> alias "foo". >>> >>> Once I rewrote the query to use TARGET and EXCLUDED correctly, I've put this >>> through an adaptation of my usual torture test, and it ran fine until >>> wraparound shutdown. I'll poke at it more later. >> >> Oops. I agree with your diagnosis, and will circle around to fix that >> bug in the next revision > > Attached patch fixes the bug. I'm not delighted about the idea of > cutting off parent parse state (the parse state of the insert) within > transformUpdateStmt() only once we've used the parent state to > establish that this is a "speculative"/auxiliary update, but it's > probably the path of least resistance here. > > When this is rolled into the next version, there will be a testcase. Looking at this thread, the last version of this patch is available here: http://www.postgresql.org/message-id/CAM3SWZRvkCKc=1Y6_Wn8mk97_Vi8+j-aX-RY-=msrjvu-ec...@mail.gmail.com And they do not apply correctly, so this patch needs a rebase. Regards, -- Michael
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
