Re: pg_receivewal starting position

From: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: Re: pg_receivewal starting position
Date: 2021-10-26 06:27:47
Message-ID: 1914572.usQuhbGJ8B@aivenronan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le mardi 26 octobre 2021, 03:15:40 CEST Michael Paquier a écrit :
> I have changed the patch per Ronan's suggestion to have the version
> check out of GetSlotInformation(), addressed what you have reported,
> and the result looked good. So I have applied this part.

Thanks !
>
> What remains on this thread is the addition of new tests to make sure
> that pg_receivewal is able to follow a timeline switch. Now that we
> can restart from a slot that should be a bit easier to implemented as
> a test by creating a slot on a standby. Ronan, are you planning to
> send a new patch for this part?

Yes, I will try to simplify the logic of the patch I sent last week. I'll keep
you posted here soon.

--
Ronan Dunklau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayk Manukyan 2021-10-26 06:49:31 Re: Feature request for adoptive indexes
Previous Message Amit Kapila 2021-10-26 06:16:35 Re: Skipping logical replication transactions on subscriber side