Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs
Date
Msg-id 31505.1550291524@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Feb 15, 2019 at 05:03:29PM +0100, Peter Eisentraut wrote:
>> Yeah, I'm OK on that, but that's not really the problem here.  This is
>> not a case where a later step in a complex DDL command needs to see what
>> an earlier step did.  This is about that something later in the
>> transaction needs to see what happened earlier in the transaction.  This
>> does not seem to be the job of each individual DDL command; they don't
>> know what someone later might want to look at.  Otherwise many DDL
>> command implementations are lacking this CCI.  I think the CCI should be
>> more like at the end of ProcessUtility().

> Not all utility commands need a CCI, for example take VACUUM.

BEGIN and COMMIT are more convincing counterexamples ...

            regards, tom lane


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15638: pg_basebackup with --wal-method=stream incorrectly generates WAL segment created during backup
Next
From: Michael Paquier
Date:
Subject: Re: BUG #15638: pg_basebackup with --wal-method=stream incorrectlygenerates WAL segment created during backup