| From: | Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Maxim Orlov <orlovmg(at)gmail(dot)com> |
| Cc: | Evgeny Voropaev <evgeny(dot)voropaev(at)tantorlabs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Date: | 2025-07-04 09:25:03 |
| Message-ID: | d8db53f0-6343-4508-8bcc-07a878d136f6@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
04.07.2025 11:31, Andrey Borodin wrote:
>
>
>> On 2 Jul 2025, at 18:38, Maxim Orlov <orlovmg(at)gmail(dot)com> wrote:
>>
>> If you
>> know of any real problems, please tell me
>
> If I understood correctly, pages can differ on primary and standby. That might be problematic for WAL debug tests.
They may differ. They differ even now. It is normal.
That is why when you enable "wal_consistency_checking" (developer option,
not present in sample postgresql.conf), pages are masked: allowed to be
different pieces are zeroed (pages hint bits, tuple hint bits, space
between pd_lower and pd_upper).
Before last version, empty space between tuples with
"repair_fragmentation=false" was certainly possible source of difference
not masked by standard mask procedure. But now those holes are zeroed.
--
regards
Yura Sokolov aka funny-falcon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2025-07-04 09:46:55 | Remove unused wait_event_info parameter in FileStartReadV() |
| Previous Message | 邱宇航 | 2025-07-04 09:22:31 | Wrong off type in smgrfd and mdfd |