Re: pg_receivexlog and replication slots - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_receivexlog and replication slots
Date
Msg-id CAB7nPqT7+o1zi4y4-_jgGZAXusgh2uSNK4paBDZvizY-fsG-FA@mail.gmail.com
Whole thread Raw
In response to Re: pg_receivexlog and replication slots  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: pg_receivexlog and replication slots
Re: pg_receivexlog and replication slots
List pgsql-hackers
On Fri, Aug 15, 2014 at 5:17 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Thanks for your review.
>
> On Fri, Aug 15, 2014 at 12:56 AM,  <furuyao@pm.nttdata.co.jp> wrote:
>> At consistency with pg_recvlogical, do you think about --start?
> I did not add that for the sake of backward-compatibility as in
> pg_recvlogical an action is mandatory. It is not the case now of
> pg_receivexlog.
>
>> [postgres postgresql-6aa6158]$ make > /dev/null
>> streamutil.c: In function 'CreateReplicationSlot':
>> streamutil.c:244: warning: suggest parentheses around '&&' within '||'
> I see. Here is a rebased patch.

Looking more at the code, IDENTIFY_SYSTEM management can be unified
into a single function. So I have written a newer version of the patch
grouping IDENTIFY_SYSTEM call into a single function for both
utilities, fixing at the same time a couple of other issues:
- correct use of TimelineID in code
- IDENTIFY_SYSTEM checks were incorrect (even in HEAD). The following
check was done but in 9.4 this command returns 4 fields:
(PQntuples(res) != 1 || PQnfields(res) < 3)
That's not directly related to this patch, but making some corrections
is not going to hurt..

Regards,
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Incremental backup: add backup profile to base backup
Next
From: Alvaro Herrera
Date:
Subject: Re: proposal for 9.5: monitoring lock time for slow queries