| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christof Petig <christof(dot)petig(at)wtal(dot)de> |
| Cc: | pgsql-bugs(at)postgreSQL(dot)org |
| Subject: | Re: [BUGS] int2 unique index malfunction (btree corrupt) |
| Date: | 1999-08-22 20:57:46 |
| Message-ID: | 18665.935355466@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Christof Petig <christof(dot)petig(at)wtal(dot)de> writes:
> During development of a CIM program I frequently updated a table by its
> primary key (int2 or numeric(3)). A lot of strange messages
> 'NOTICE: (transaction aborted): queries ignored until END' alerted me
> that something is going wrong.
> [ details snipped ]
FWIW, the test program you supplied seems to run without errors for me.
I'm using current CVS sources on an HPUX box.
There was a fix applied on 8/8 to clean up a problem with btrees not
recovering from an aborted transaction properly, but I'm not sure
whether that has anything to do with your example...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christof Petig | 1999-08-23 12:22:00 | Re: [BUGS] int2 unique index malfunction (btree corrupt) |
| Previous Message | Krzysztof Czuma | 1999-08-22 15:01:17 |