Re: unlogged sequences
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, "David G. Johnston" <david.g.johnston@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-04-01T17:41:53Z
Lists: pgsql-hackers
On Fri, Apr 1, 2022 at 12:31 PM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: > > An "internal" dependency means that the internal object shouldn't really > > be operated on directly. (In some cases it's allowed for convenience.) > > So I think in that case the sequence must follow the table's persistence > > in all cases. This is accomplished by setting the initial persistence > > to the table's, making ALTER TABLE propagate persistence changes, and > > prohibiting direct ALTER SEQUENCE SET. > > But to make pg_upgrade work for identity sequences of unlogged tables, > we need to allow ALTER SEQUENCE ... SET LOGGED on such sequences. Which > I guess is not a real problem in the end. And I think also SET UNLOGGED, since it would be weird IMHO to make such a change irreversible. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
Unlogged sequences
- 344d62fb9a97 15.0 landed
-
Preparatory test cleanup
- ae63017bdb31 15.0 landed