From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | twoflower <standa(dot)kurik(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: Server tries to read a different config file than it is supposed to |
Date: | 2015-05-23 22:23:12 |
Message-ID: | 5560FDD0.3040904@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/23/2015 02:42 PM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> So on my Ubuntu installs it does not set up the postgres user to allow login, so how are you getting to:
>> su postgres -c ...
>
>>From root, presumably ...
Aargh, so used to the little voice telling me not to do things as root I
forgot that possibility.
>
> I thought of a different theory: maybe the server's complaint is not due
> to trying to read that file as a config file, but it's just because there
> is an unreadable/unwritable file in the data directory. See Christoph
> Berg's complaint at
> http://www.postgresql.org/message-id/20150523172627.GA24277@msg.df7cb.de
>
> This would only apply if the OP was trying to use this week's releases
> though. Also, I thought the fsync-everything code would only run if
> the server had been shut down uncleanly. Which maybe it was, but that
> bit of info wasn't provided either.
>
> regards, tom lane
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Marcos Ortiz | 2015-05-23 22:27:37 | Trying to solve a SocketError [Errno 13] Permission with PL/Python in PostgreSQL 9.3 |
Previous Message | Daniel Begin | 2015-05-23 22:16:43 | Re: FW: Constraint exclusion in partitions |