| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: unlogged sequences |
| Date: | 2022-03-31 21:11:56 |
| Message-ID: | CAKFQuwZaYADWjvyp2zY1sshhHZ3U4RJgVP6ht56G4BR68SbWow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 31, 2022 at 1:40 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-31 21:12:33 | Re: proposal: enhancing plpgsql debug API - returns text value of variable content |
| Previous Message | Andres Freund | 2022-03-31 21:04:16 | Re: Higher level questions around shared memory stats |