Re: replication slot restart_lsn initialization

From: Andres Freund <andres(at)anarazel(dot)de>
To: Gurjeet Singh <gurjeet(at)singh(dot)im>
Cc: "Duran, Danilo" <danilod(at)amazon(dot)com>, "robertmhaas(at)gmail(dot)com" <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: replication slot restart_lsn initialization
Date: 2015-08-11 23:20:01
Message-ID: 20150811232001.GB8470@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-08-11 15:59:59 -0700, Gurjeet Singh wrote:
> In your version, I don't see a comment that refers to the fact that it
> works on the currently active (global variable) slot.

Hm?

/*
* Reserve WAL for the currently active slot.
*
* Compute and set restart_lsn in a manner that's appropriate for the type of
* the slot and concurrency safe.
*/
> > I moved
> > values[0] = NameGetDatum(&MyReplicationSlot->data.name);
> > nulls[0] = false;
> > to outside the conditional block, there seems no reason to have it in
> > there?
> >
>
> The assignment to values[0] is being done twice. We can do away with the
> one in the else part of the if condition.

Ugh, that's a mistake.

> [1]: I altered you to it in a personal email, but probably it fell through
> the cracks.

I usually just check the lists for newer patch versions, sorry...

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-08-12 00:27:21 Re: GIN pending clean up is not interruptable
Previous Message Gurjeet Singh 2015-08-11 22:59:59 Re: replication slot restart_lsn initialization