Re: PG Upgrade with hardlinks, when to start/stop master and replicas - Mailing list pgsql-general

From Tom Lane
Subject Re: PG Upgrade with hardlinks, when to start/stop master and replicas
Date
Msg-id 4533.1550811780@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG Upgrade with hardlinks, when to start/stop master and replicas  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG Upgrade with hardlinks, when to start/stop master and replicas  (Martín Fernández <fmartin91@gmail.com>)
List pgsql-general
Bruce Momjian <bruce@momjian.us> writes:
> On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
>> * Bruce Momjian (bruce@momjian.us) wrote:
>>> There was too much concern that users would accidentally start the old
>>> server at some later point, and its files would be hard linked to the
>>> new live server, leading to disaster.

>> Sure, I understand that concern, just wish there was a better approach
>> we could use for "DO NOT START THIS SERVER" rather than moving of the
>> pg_control file.

> As ugly as it is, I have never heard of a better solution.

system("rm -rf $OLDPGDATA") ... nah, that is not a better idea.

            regards, tom lane


pgsql-general by date:

Previous
From: github kran
Date:
Subject: Re: Postgresql RDS DB Latency Chossing Hash join Plan
Next
From: github kran
Date:
Subject: How many billion rows of data I can store in PostgreSQL RDS.