| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Abhishree hn <abhishreehn(at)crgroup(dot)co(dot)in> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16261: Not able to start Postgres |
| Date: | 2020-02-17 13:57:10 |
| Message-ID: | 8D94A244-2F6D-45DA-A8FB-560305A63743@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 17 Feb 2020, at 14:17, Abhishree hn <abhishreehn(at)crgroup(dot)co(dot)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(at)yesql(dot)se> wrote:
> > On 17 Feb 2020, at 14:10, Abhishree hn <abhishreehn(at)crgroup(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-02-17 14:04:52 | Re: Adding libpgcommon and libpgcore to libpq pkg-config's Requires.private |
| Previous Message | PG Bug reporting form | 2020-02-17 13:52:53 | BUG #16263: pg_advisory_xact_lock cannot be released |