| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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 02:31:32 |
| Message-ID: | 20190222023132.GP6197@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greetings,
* Bruce Momjian (bruce(at)momjian(dot)us) wrote:
> On Tue, Feb 19, 2019 at 12:25:24PM -0500, Stephen Frost wrote:
> > Ah, right, I forgot that it did that, fair enough.
> >
> > I've never been thrilled with that particular approach due to the
> > inherent risks of people messing directly with files like pg_control,
> > but that's how it is for now.
>
> 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.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-02-22 02:33:52 | Re: PG Upgrade with hardlinks, when to start/stop master and replicas |
| Previous Message | Bruce Momjian | 2019-02-22 02:07:28 | Re: PG Upgrade with hardlinks, when to start/stop master and replicas |