From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5798: Some weird error with pl/pgsql procedure |
Date: | 2011-06-14 14:55:27 |
Message-ID: | 28343.1308063327@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> I bumped into the 'virtual tuple' error on 9.0.3 on a completely
> unrelated query:
> create table foo(a int, b int);
> insert into foo select 1, 1 where not exists (select 1 from foo where
> a = 1 for update);
> 9.0.4 got rid of the error, but as there are no triggers or anything
> like that on the foo so I thought I'd post my findings here in case
> anyone else bumped into it.
I think most likely this has to do with commit
d5478c3391f8f1a243abbc3d9253aac3d6d3538e, and is unrelated (except
in the error message) to that trigger issue.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Mamin | 2011-06-14 16:31:34 | BUG #6057: regexp_replace & back references |
Previous Message | Merlin Moncure | 2011-06-14 14:39:29 | Re: BUG #5798: Some weird error with pl/pgsql procedure |