Horton

Re: unlogged sequences

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-03-31T21:11:56Z
Lists: pgsql-hackers 
On Thu, Mar 31, 2022 at 1:40 PM David G. Johnston <
david.g.johnston@gmail.com> wrote:

> The DBA just has to execute the ALTER SEQUENCE command on all relevant
> sequences.
>

Additional, if we do not implement the forced matching of persistence mode,
we should consider adding an "ALTER TABLE SET ALL SEQUENCES TO UNLOGGED"
command for convenience.  Or maybe make it a function - which would allow
for SQL execution against a catalog lookup.

David J.

Commits

  1. Unlogged sequences

  2. Preparatory test cleanup