| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: On markers of changed data |
| Date: | 2017-10-06 14:44:17 |
| Message-ID: | 20171006144417.qq3siijflogrwtep@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier wrote:
> The only sane method for Postgres is really to scan the
> page header LSNs, and of course you already know that.
I hope the idea is not to have to scan every single page in the
database, because that would be too slow. It should be possible to
build this so that a single summary LSN is kept for a largish group of
pages, allowing large portions of the database to be skipped from even
being read if they are known not to contain any page newer than the
previous backup.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2017-10-06 14:46:17 | Re: Issue with logical replication: MyPgXact->xmin already is valid |
| Previous Message | Michael Paquier | 2017-10-06 14:34:36 | Re: On markers of changed data |