Re: PostgresSQL 9.5 and systemd autorestart but without replication. - Mailing list pgsql-admin

From Poul Kristensen
Subject Re: PostgresSQL 9.5 and systemd autorestart but without replication.
Date
Msg-id CAAOuvVoMpaXNm32n=3QHG2vdmMfCMpeWFx=YzCJF8bAu_h1VLw@mail.gmail.com
Whole thread Raw
In response to Re: PostgresSQL 9.5 and systemd autorestart but without replication.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgresSQL 9.5 and systemd autorestart but without replication.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
It  IS the standby server:

Result of pg_isready:

/usr/pgsql-9.6/bin/pg_isready -h /tmp -p 5432
/tmp:5432 - rejecting connections

In the pg_log:

2016-10-26 13:30:16.298 UTC > FATAL:  the database system is starting up


Thanks
Poul


2016-10-26 15:10 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Poul Kristensen <bcc5226@gmail.com> writes:
> Replica(hot_standby) server:
> Is it normal behavior that PostgreSQL 9.6 does  a very very slow
> recovery restart point at 1/77472E5 in the pg_log
> while doing this
>  postgres: startup process   recovering 000000010000000100000077(this
> process has run several days)

If that's the standby server, that process will persist as long as it's in
standby; it's what's responsible for applying WAL received by the
walreceiver process.  You should have been able to connect long before
now, though.

                        regards, tom lane



--
Med venlig hilsen / Best regards
Poul Kristensen
Linux-OS/Virtualizationexpert and Oracle DBA

pgsql-admin by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Using pg hotbackup directly without wal archives
Next
From: Tom Lane
Date:
Subject: Re: PostgresSQL 9.5 and systemd autorestart but without replication.