Re: pgsql: Integrate recovery.conf into postgresql.conf

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Sergei Kornilov <sk(at)zsrv(dot)org>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Integrate recovery.conf into postgresql.conf
Date: 2018-11-26 19:12:53
Message-ID: 20181126191253.GZ3415@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Greetings,

* Sergei Kornilov (sk(at)zsrv(dot)org) wrote:
> > I think I would have done 'if (targetSettingsCount != 1)' here.
> Streaming replication does not have any recovery_target.
> Well, i can check StandbyModeRequested too and allow 0 recovery_target only for standby mode.

Ah. Agreed.

> >>  -# Multiple targets
> >>  -# Last entry has priority (note that an array respects the order of items
> >>  -# not hashes).
> >
> > You could (and imv should) include a test that throws an expected error
> > if multiple targets are specified.
> We have some example for checking unable-to-start DB? Did not find yet

The TAP system in general supports expected failures, but that might
only be with the simple binaries, not sure. I know src/bin/pg_dump has
those though.

> > Let’s at least fix the currently committed patch before adding new features or changing how things in recovery work.
> +1

Thanks!

Stephen

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David Steele 2018-11-26 19:36:56 Re: pgsql: Integrate recovery.conf into postgresql.conf
Previous Message Sergei Kornilov 2018-11-26 18:34:38 Re: pgsql: Integrate recovery.conf into postgresql.conf

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2018-11-26 19:36:56 Re: pgsql: Integrate recovery.conf into postgresql.conf
Previous Message Daniel Verite 2018-11-26 19:01:20 Re: csv format for psql