| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, dnsl48(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs |
| Date: | 2019-03-12 03:46:30 |
| Message-ID: | 20190312034630.GH13812@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 11, 2019 at 09:41:14PM +0100, Peter Eisentraut wrote:
> I looked into backpatching this, but the test case doesn't fail in PG10.
> I ran a round of bisecting but didn't arrive at a sensible result. The
> test case appears to be a bit random in its failure modes. The issue
> could in principle extend further back, since the code in question isn't
> really new. Any ideas or suggestions?
I can reproduce the issue on a v10 server, for example:
=# create temporary table foo ( bar int generated by default as identity ) on
commit drop;
CREATE TABLE
=# \q
$ psql
=# create temporary table a (b varchar);
ERROR: XX000: could not open relation with OID 16389
Perhaps you did not start with a fresh server or did not reset the
connection properly? This counts.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sandeep Thakkar | 2019-03-12 07:31:59 | Re: Installation issue |
| Previous Message | Peter Eisentraut | 2019-03-11 20:41:14 | Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs |