Re: [HACKERS] Function to move the position of a replication slot - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Function to move the position of a replication slot
Date
Msg-id 20170905025148.6tneoeoppxo246qk@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Function to move the position of a replication slot  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Function to move the position of a replication slot
List pgsql-hackers
On 2017-09-05 11:36:47 +0900, Michael Paquier wrote:
> On Thu, Aug 31, 2017 at 9:19 PM, Magnus Hagander <magnus@hagander.net> wrote:
> > PFA an updated and rebased patch.
> >
> > Rebased. Now named pg_advance_replication_slot. ERROR on logical slots.
> > Forward only.
> >
> > I think that, in the end, covered all the comments?
> 
> +   if (backwards)
> +       ereport(WARNING,
> +               (errmsg("Not moving replication slot backwards!")));
> Shouldn't this be an ERROR, mentioning the current position of the slot?
> 
> +        ereport(ERROR,
> +                (errmsg("Only physical replication slots can be advanced.")));
> ERRCODE_FEATURE_NOT_SUPPORTED, no?

Seither of these seem to follow the message guidelines.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Function to move the position of a replication slot
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands