PostgreSQL starting with a corrupted database or other fatal issues

Assuming that PostgreSQL is started by systemd, and encounters fatal issues, how often does systemd attempt to re-start it before giving up? I'm not familiar with that interaction and if systemd stops after X attempts, or what. What does postgres do when it encounters fatal issues and cannot star

Re: Customer unable to connect on port 5432, Postgres 10.7

Failed to copy pgsql-general, post repeated below: Adrian, I used your suggestions, fixed the column order, and it worked the first time for the customer this morning: hosttestpgdbpgusereee.fff.ggg.1/24password THANKS!

Customer unable to connect on port 5432, Postgres 10.7

Hello again Postgres friends, Customer is unable to log in to a PG database on 5432 using a Windows client. Output of my test sessions below, I think the problem may be lines 3 - 7 but no idea. Ideas greatly appreciated! Lines 1,2 PG Log entries Lines 3-7 pg_hba.conf entries Lines 8-10 postgresq

See what options a Postgresql binary was compiled with

Planning to convert a Postgres 10 instance to systemd init. I understand it had to be compiled with systemd support to work that way. Thanks!

Re: Changing the data directory path before the initial configuration of PostgreSQL 10.7.1

> The easiest way is moving /var/lib/pgsql/data under /xyz directory > (when the db is not running) and create a symlink in the original > location: > > chown postgres: /xyz > su - postgres > mv /var/lib/pgsql/data /xyz/10-data > ln -s /xyz/10-data /var/lib/pgsql/data > > Then you can use setup scr

Changing the data directory path before the initial configuration of PostgreSQL 10.7.1

Hi Postgres friends, Using Postgres 10.7.1 on Fedora core 28. Admittedly not the latest but am helping a colleague with a production system who needs a PostgreSQL instance on this machine. The default /var/lib/pgsql/data directory needs to go on another partition with more space, let's call it /