| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On markers of changed data |
| Date: | 2017-10-06 14:22:11 |
| Message-ID: | 5126.1507299731@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrey Borodin <x4mmm(at)yandex-team(dot)ru> writes:
> Is it safe to use file modification time to track that file were changes
> since previous backup?
I'd say no:
1. You don't know the granularity of the filesystem's timestamps, at least
not without making unportable assumptions.
2. There's no guarantee that the system clock can't be set backwards.
3. It's not uncommon for filesystems to have optimizations whereby they
skip or delay some updates of file mtimes. (I think this is usually
optional, but you couldn't know whether it's turned on.)
#2 is probably the worst of these problems.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-06 14:34:36 | Re: On markers of changed data |
| Previous Message | Stephen Frost | 2017-10-06 14:11:40 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |