On Wed, Nov 7, 2018 at 11:30:18AM +1100, 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
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?
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
On 11/5/18 9:27 PM, rob stone wrote:
Hello,
Trying to run pg_upgrade from version 10 to version 11 on the test
server and pulling the following error:-
could not open version file: /home/postgres/testing/data_v10/PG_VERSION
Failure, exiting
O/S is:- Debian 4.18.10-2 (2018-11-02) x86_64 GNU/Lin
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 sho
Hello,
Trying to run pg_upgrade from version 10 to version 11 on the test
server and pulling the following error:-
could not open version file: /home/postgres/testing/data_v10/PG_VERSION
Failure, exiting
O/S is:- Debian 4.18.10-2 (2018-11-02) x86_64 GNU/Linux
Running pg_upgrade as user postgres
