Re: refactor subscription tests to use PostgresNode'swait_for_catchup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: refactor subscription tests to use PostgresNode'swait_for_catchup
Date
Msg-id 20180111032437.GA994@paquier.xyz
Whole thread Raw
In response to Re: refactor subscription tests to use PostgresNode'swait_for_catchup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: refactor subscription tests to use PostgresNode'swait_for_catchup
List pgsql-hackers
On Wed, Jan 10, 2018 at 09:45:56PM -0500, Peter Eisentraut wrote:
> On 1/8/18 23:47, Michael Paquier wrote:
> Should we just remove it?  Apparently, it was never functional to begin
> with.  Otherwise, we'd have to write a second query to return the value
> to print.  wait_for_slot_catchup has the same issue.  Seems like a lot
> of overhead for something that has never been used.

Fine for me to remove it.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: refactor subscription tests to use PostgresNode'swait_for_catchup
Next
From: Noah Misch
Date:
Subject: Re: pl/perl extension fails on Windows