From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Benedikt Grundmann <bgrundmann(at)janestreet(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Problems with pg_upgrade after change of unix user running db. |
Date: | 2015-11-23 16:19:29 |
Message-ID: | 56533C91.1050509@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/23/15 5:12 AM, Benedikt Grundmann wrote:
> So I would love to know what the recommended way to go forward is.
> Ideally it avoids using the old postgres unix
> and database user (we want to completely get rid of it eventually, but
> if I have to do some additional one off work this
> time to get past this hurdle using the user that is of course an
> acceptable trade off).
Can you provide a test script that demonstrates the problem?
The unix user that runs the database processes is pretty inconsequential
to Postgres (as long as it's not root). There's generally no need for
any correlation between unix accounts and database accounts. initdb uses
the unix account running initdb for the initial database account, but as
you've seen you can over-ride that.
pg_upgrade does care about unix accounts though (since it's dealing
directly with the file system). It also needs to be able to connect to
both databases, so it needs valid database login credentials as well.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-11-23 16:31:42 | Re: using a postgres table as a multi-writer multi-updater queue |
Previous Message | Kevin Grittner | 2015-11-23 15:30:15 | Re: ??: postgres cpu 100% need help |