Joe Conway wrote: > On 09/29/2015 01:48 PM, Alvaro Herrera wrote: > > I remember it, but I'm not sure it would have helped you. As I recall, > > your trouble was that after a reboot the init script decided to initdb > > the mount point -- postmaster wouldn't have been running at all ... > > Right, which the init script non longer does as far as I'm aware, so > hopefully will never happen again to anyone.
Yeah. > But it was still a case where the postmaster started on one copy of > PGDATA (the newly init'd copy), and then the contents of the real PGDATA > was swapped in (when the filesystem was finally mounted), causing > corruption to the production data. Ah, I didn't remember that part of it, but it makes sense. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
