| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal |
| Date: | 2024-07-17 13:44:01 |
| Message-ID: | CA+Tgmob6MSyKPQQ2QfKVznLHz1-Dg2AoZxjUoz80PTYXq14gRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 16, 2024 at 1:16 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> I don't have another solution that can be pushed into v17. I understand
> the risks raised so far, so I'm okay with just pushing the "fast_forward" patch.
> It might be helpful to add a note to the summarize_wal documentation,
> for example, "summarize_wal can be enabled after startup with wal_level = minimal,
> but WAL generated at this level won't be summarized."?
Here is v5. This version differs from v4 in that it updates the
documentation for summarize_wal and pg_get_wal_summarizer_state(). The
previous version made no documentation changes.
--
Robert Haas
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Do-not-summarize-WAL-if-generated-with-wal_level-.patch | application/octet-stream | 21.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-07-17 13:49:26 | Re: filesystem full during vacuum - space recovery issues |
| Previous Message | Ashutosh Sharma | 2024-07-17 13:31:56 | Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions |