| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade and rsync |
| Date: | 2015-01-29 17:42:49 |
| Message-ID: | 54CA7119.40406@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/29/2015 09:11 AM, Bruce Momjian wrote:
> On Thu, Jan 29, 2015 at 12:09:58PM -0500, Andrew Dunstan wrote:
>> Then step 2 should specify that it's for the master.
>
> Right. Josh is just listing all the steps --- the pg_upgrade docs
> already have that spelled out in detail.
What I'm also saying is that, if we expect anyone to be able to follow
all of these steps, it has to be very explicit; just saying "Follow the
pg_upgrade docs but don't start the master yet" isn't clear enough,
because the pg_upgrade docs have a few alternative paths.
On the whole, I personally would never follow this procedure at a
production site. It's way too fragile and easy to screw up.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-01-29 17:49:29 | Re: pg_check_dir comments and implementation mismatch |
| Previous Message | Robert Haas | 2015-01-29 17:37:25 | Re: pg_check_dir comments and implementation mismatch |