Re: BUG #16261: Not able to start Postgres - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: BUG #16261: Not able to start Postgres
Date
Msg-id 8D94A244-2F6D-45DA-A8FB-560305A63743@yesql.se
Whole thread Raw
In response to BUG #16261: Not able to start Postgres  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
> On 17 Feb 2020, at 14:17, Abhishree hn <abhishreehn@crgroup.co.in> wrote:
>
> Hi Daniel,
>
> There is no such directory exist.

That's quite likely a contributing factor to the problems you're facing.
Either reconfigure to use an alternative directory or make sure this one exists
and is writeable.

> On Mon, Feb 17, 2020 at 6:46 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> > On 17 Feb 2020, at 14:10, Abhishree hn <abhishreehn@crgroup.co.in> wrote:
> >
> > Hi ,
> > Yes, We are not able to start the database.
> > can you please tell me which directory exitance you are talking about?
>
> The logs you posted show it in full detail: /var/run/postgresql/.s.PGSQL.5432.lock




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16263: pg_advisory_xact_lock cannot be released
Next
From: Tom Lane
Date:
Subject: Re: Adding libpgcommon and libpgcore to libpq pkg-config's Requires.private