From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | stemy(at)stemy(dot)me |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16564: Can't start the service postgresql@11-main.service |
Date: | 2020-07-30 22:05:48 |
Message-ID: | 1651099.1596146748@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> I can't use any server app that requires a postgresql database.
> I can't even start the service. It is marked as "inactive (dead)", and if i
> execute "systemctl start postgresql(at)11-main(dot)service", it returns me this:
> "Assertion failed on job for postgresql(at)11-main(dot)service(dot)".
Well, the error message says that the cluster configuration file
isn't there:
> AssertPathExists=/etc/postgresql/11/main/postgresql.conf was not
> met
So I wonder whether you initialized the database at all; normally
that action would set up a postgresql.conf file as a byproduct.
With a bare Postgres installation you'd run initdb for that purpose.
But since you're apparently using Debian's packaging of Postgres,
I'd recommend using whatever script they provide for the purpose.
Reading the package's documentation would tell you that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-07-31 00:14:21 | Re: BUG #16558: `AND FALSE` increases planning time of query on 2 tables with 1000 partitions to more than 7 seconds |
Previous Message | Thomas Munro | 2020-07-30 21:37:01 | Re: BUG #16563: Потерлись данные таблиц POS |