Re: Logical decoding on standby

From: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "Okano, Naoki" <okano(dot)naoki(at)jp(dot)fujitsu(dot)com>
Subject: Re: Logical decoding on standby
Date: 2016-12-21 06:37:43
Message-ID: 9fa814da-1dcd-68ad-eb8e-457085f14715@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21/12/16 04:31, Craig Ringer wrote:
> On 20 December 2016 at 15:03, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> wrote:
>
>> But in 0003 I don't understand following code:
>>> + if (endpos != InvalidXLogRecPtr && !do_start_slot)
>>> + {
>>> + fprintf(stderr,
>>> + _("%s: cannot use --create-slot or --drop-slot together with --endpos\n"),
>>> + progname);
>>> + fprintf(stderr, _("Try \"%s --help\" for more information.\n"),
>>> + progname);
>>> + exit(1);
>>> + }
>>
>> Why is --create-slot and --endpos not allowed together?
>
> Actually, the test is fine, the error is just misleading due to my
> misunderstanding.
>
> The fix is simply to change the error message to
>
> _("%s: --endpos may only be specified
> with --start\n"),
>
> so I won't post a separate followup patch.
>

Ah okay makes sense. The --create-slot + --endpos should definitely be
allowed combination, especially now that we can extend this to
optionally use temporary slot.

--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-12-21 06:47:45 Re: Logical decoding on standby
Previous Message Andrew Borodin 2016-12-21 06:26:57 Re: pg_background contrib module proposal