| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | 'David Steele' <david(at)pgmasters(dot)net>, "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>, "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Enhance traceability of wal_level changes for backup management |
| Date: | 2021-03-16 01:00:16 |
| Message-ID: | ffff1f75375c3146a2ca8e0ccabba044f56d60c1.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2021-03-15 at 17:32 -0400, Stephen Frost wrote:
> We explicitly document that people can switch the WAL level and restart
> to do bulk data loads faster, and there's certainly no shortage of
> discussion (including what prompted this thread..) about doing exactly
> that. Adding more documentation around that would certainly be good,
> as would changing this:
>
> ereport(WARNING,
> (errmsg("WAL was generated with wal_level=minimal, data may be missing"),
> errhint("This happens if you temporarily set wal_level=minimal without taking a new base backup.")));
>
> into a PANIC instead of a WARNING.
There is a patch in the commitfest that does exactly that (except it
uses ERROR rather than PANIC):
https://postgr.es/m/OSBPR01MB4888CBE1DA08818FD2D90ED8EDF90@OSBPR01MB4888.jpnprd01.prod.outlook.com
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-03-16 01:00:37 | Re: Improvements and additions to COPY progress reporting |
| Previous Message | Tom Lane | 2021-03-16 00:30:18 | Re: [PATCH]: Allow errors in parameter values to be reported during the BIND phase itself.. |