Re: pg_dump, pg_dumpall and data durability
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>,
Michael Paquier <michael.paquier@gmail.com>
Cc: Albe Laurenz <laurenz.albe@wien.gv.at>,
PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2016-11-13T03:00:35Z
Lists: pgsql-hackers
On 11/8/16 3:48 PM, Robert Haas wrote: > First question: Do we even want this? Generally, when a program > writes to a file, we rely on the operating system to decide when that > data should be written back to disk. We have to override that > distinction for things internal to PostgreSQL because we need certain > bits of data to reach the disk in a certain order, but it's unclear to > me how far outside the core database system we want to extend that. I had voiced a similar concern previously: https://www.postgresql.org/message-id/f8dff810-f5f4-77c3-933b-127df4ed94e5@2ndquadrant.com At the time, there were no other comments, so we went ahead with it, which presumably gave encouragement to pursue the current patch. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Sync pg_dump and pg_dumpall output
- 96a7128b7b4c 10.0 landed