diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2019-04-29 08:44:51 +0200 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2019-04-29 08:49:22 +0200 |
commit | 10b2675d6e79ad76f2b74c569f4cf1a716a904c1 (patch) | |
tree | d0435f0d7721c4fd311e8097b8c4f49416e87e9a /src/backend/access/gist/gistget.c | |
parent | c25e638b1800752fad99d487a3c805db4980db94 (diff) | |
download | postgresql-10b2675d6e79ad76f2b74c569f4cf1a716a904c1.tar.gz postgresql-10b2675d6e79ad76f2b74c569f4cf1a716a904c1.zip |
Fix potential catalog corruption with temporary identity columns
If a temporary table with an identity column and ON COMMIT DROP is
created in a single-statement transaction (not useful, but allowed),
it would leave the catalog corrupted. We need to add a
CommandCounterIncrement() so that PreCommit_on_commit_actions() sees
the created dependency between table and sequence and can clean it
up.
The analogous and more useful case of doing this in a transaction
block already runs some CommandCounterIncrement() before it gets to
the on-commit cleanup, so it wasn't a problem in practical use.
Several locations for placing the new CommandCounterIncrement() call
were discussed. This patch places it at the end of
standard_ProcessUtility(). That would also help if other commands
were to create catalog entries that some on-commit action would like
to see.
Bug: #15631
Reported-by: Serge Latyntsev <dnsl48@gmail.com>
Author: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Reviewed-by: Michael Paquier <michael@paquier.xyz>
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions