RE: Follow-up fixes for online wal_level change - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Follow-up fixes for online wal_level change
Date
Msg-id OS9PR01MB12149AD5A8A9FF83DC4F6CF4BF5C62@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread
Responses Re: Follow-up fixes for online wal_level change
List pgsql-hackers
Dear Fujii-san,

> Should this status be exposed also by pg_control_checkpoint()?

Oh I didn't know the function, yes, seems to be exposed as well.

While checking the function, I found that CheckPoint:: wal_level is not
shown by the code function as well. Should we handle that?
I think pg_controldata command does not have to output the attribute because
ControlFileData::wal_level is also printed, but not sure the SQL function.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Re: Fix duplicate detection for null-treatment window functions
Next
From: wenhui qiu
Date:
Subject: Re: [PATCH] Refactor SLRU to always use long file names