From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Running pg_upgrade Version 11 |
Date: | 2018-11-07 05:13:49 |
Message-ID: | 5d413da9-250c-3bcd-e979-0d0db83aa28c@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/06/2018 06:30 PM, rob stone wrote:
>
> On Tue, 2018-11-06 at 15:17 +0900, Michael Paquier wrote:
>> On Tue, Nov 06, 2018 at 04:27:35PM +1100, rob stone wrote:
>>> Logged in as user postgres and postgres owns the files created by
>>> initdb, so is this a permissions problem or am I having a brain
>>> fade?
>> Having 0600 as umask for those files is normal. Don't you have more
>> logs about the error? You should not see this error, except if
>> data_v10
>> is not a data folder initialized correctly, so perhaps you messed up
>> something in your environment?
>> --
>> Michael
>
>
> Problem caused by my eyesight.
> A colleague pointed out the typo in the argument to the -d parameter.
> Working as intended.
That's why I like to line up my statements
/usr/lib/postgresql/11/bin/pg_upgrade \
-b /usr/lib/postgresql/10/bin \
-B /usr/lib/postgresql/11/bin \
-d /home/postgres/testing/data_v10 \
-D /home/postgres/testing/data_v11
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | pavan95 | 2018-11-07 05:56:10 | Re: Recovery data base!! |
Previous Message | Elson Vaz | 2018-11-07 05:13:20 | Recovery data base!! |