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

From Michael Paquier
Subject Re: BUG #15631: Generated as identity field in a temporary tablewith on commit drop corrupts system catalogs
Date
Msg-id 20190216001308.GF2240@paquier.xyz
Whole thread Raw
In response to Re: BUG #15631: Generated as identity field in a temporary table withon commit drop corrupts system catalogs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Doug Safreno
Date:
Subject: Re: Bug: Deferred FKey Check Happening on Double Update, Not Single
Next
From: PG Bug reporting form
Date:
Subject: BUG #15638: pg_basebackup with --wal-method=stream incorrectly generates WAL segment created during backup