| From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: attempted to lock invisible tuple - PG 8.4.1 |
| Date: | 2009-10-07 06:53:21 |
| Message-ID: | 6bc73d4c0910062353k2e55620sb1f396ee68429f77@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 7, 2009 at 3:09 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Stuart Bishop wrote:
>
>> >I don't think the committed patch touches anything involved in what
>> >you're testing, but if you could grab CVS tip from the 8.4 branch (or
>> >the snapshot from ftp.postgresql.org:/pub/snapshot/stable/8.4 ) and give
>> >it a try, that'd be great.
>>
>> I trigger the same error with a freshly built snapshot.
>
> If you're up for a bit of patching, please test with the attached patch
> applied.
The patch is working. I am no longer able to trigger the 'attempted to
lock invisible tuple' error.
Thanks :-)
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jamie Lawrence-Jenner | 2009-10-07 08:26:19 | SSIS and Postgres |
| Previous Message | paresh masani | 2009-10-07 05:48:47 | Need help in spi_prepare errors |