Re: unlogged sequences - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: unlogged sequences
Date
Msg-id CAKFQuwZaYADWjvyp2zY1sshhHZ3U4RJgVP6ht56G4BR68SbWow@mail.gmail.com
Whole thread Raw
In response to Re: unlogged sequences  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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.

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Higher level questions around shared memory stats
Next
From: Tom Lane
Date:
Subject: Re: proposal: enhancing plpgsql debug API - returns text value of variable content