| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, 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-08 07:52:28 |
| Message-ID: | 82661839-7346-46F3-9CCA-DF18C90453BF@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom, Alvaro, Michael, and especially Septhen, thank you for your valuable comments.
I feel enlightened about mtime.
My takeaway is:
1. Any other marker would be better (It can be WAL scan during archiving, some new LSN-based mechanics* et c.)
2. mtime could be used, with precautions described by Stephen are taken.
But my other question still seems unanswered: can I use LSN logic for incrementing FSM and VM? Seems like most of the time there is valid LSN
* I like the idea of using something for both incr(diff) backups and VACUUM, it worth thinking about.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-10-08 13:00:31 | Re: Slow synchronous logical replication |
| Previous Message | Tom Lane | 2017-10-08 00:23:09 | Re: Prepared statements assume text type in PG10 |