Re: refactor subscription tests to use PostgresNode's wait_for_catchup

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: refactor subscription tests to use PostgresNode's wait_for_catchup
Date: 2018-01-11 03:24:38
Message-ID: 20180111032437.GA994@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2018-01-11 05:08:20 Re: pl/perl extension fails on Windows
Previous Message Peter Eisentraut 2018-01-11 02:45:56 Re: refactor subscription tests to use PostgresNode's wait_for_catchup