| From: | "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Fix of fake unlogged LSN initialization |
| Date: | 2019-10-19 05:03:00 |
| Message-ID: | OSBPR01MB2503CE851940C17DE44AE3D9FE6F0@OSBPR01MB2503.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
The attached trivial patch fixes the initialization of the fake unlogged LSN. Currently, BootstrapXLOG() in initdb sets the initial fake unlogged LSN to FirstNormalUnloggedLSN (=1000), but the recovery and pg_resetwal sets it to 1. The patch modifies the latter two cases to match initdb.
I don't know if this do actual harm, because the description of FirstNormalUnloggedLSN doesn't give me any idea.
Regards
Takayuki Tsunakawa
| Attachment | Content-Type | Size |
|---|---|---|
| init-fake-unlogged-lsn.patch | application/octet-stream | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2019-10-19 05:41:24 | Re: jsonb_set() strictness considered harmful to data |
| Previous Message | Pavel Stehule | 2019-10-19 04:17:39 | Re: jsonb_set() strictness considered harmful to data |