| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Martín Fernández <fmartin91(at)gmail(dot)com>, Hellmuth Vargas <hivs77(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG Upgrade with hardlinks, when to start/stop master and replicas |
| Date: | 2019-02-22 05:03:00 |
| Message-ID: | 4533.1550811780@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Feb 21, 2019 at 09:31:32PM -0500, Stephen Frost wrote:
>> * Bruce Momjian (bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | github kran | 2019-02-22 05:08:30 | How many billion rows of data I can store in PostgreSQL RDS. |
| Previous Message | github kran | 2019-02-22 04:57:35 | Re: Postgresql RDS DB Latency Chossing Hash join Plan |