From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | michael(at)syncinc(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #796: Problem after upgrading to v. 723 |
Date: | 2002-10-12 16:22:10 |
Message-ID: | 12561.1034439730@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
pgsql-bugs(at)postgresql(dot)org writes:
> After upgrading from v. 721 to 723 some of regression tests failed.
> BEGIN;
> CREATE SEQUENCE s_ASeq;
> SELECT nextval('s_ASeq') ;
> DROP SEQUENCE s_ASeq ;
> /* some sql statement might be here */
> COMMIT;
> 1) Problem occurs when attempt is made to drop the sequence:
> ERROR: RelationForgetRelation: relation <rel_no> is still open
Yes; 7.2.3 will basically not let you drop a sequence that was touched
in the current transaction. This was a hack added to prevent core dumps
of the sort illustrated in bug #671,
http://archives.postgresql.org/pgsql-bugs/2002-05/msg00106.php
http://archives.postgresql.org/pgsql-bugs/2002-05/msg00113.php
There is a proper fix in 7.3, but it was deemed too risky to back-patch
into the 7.2 series.
I am surprised that you did not have horrible stability problems under
previous releases, if your application was in the habit of issuing
transactions like the above.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-12 22:36:10 | Re: Bug #795: null resulting from left join corrupts select |
Previous Message | pgsql-bugs | 2002-10-12 14:23:50 | Bug #796: Problem after upgrading to v. 723 |