From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | pg_recvlogical tests |
Date: | 2014-05-15 21:09:14 |
Message-ID: | 20140515210914.GF16014@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I have some preliminary tests for the pg_recvlogical binary using the
infrastructure Peter added. I am wondering if somebody has a good idea
about how to make the tests more meaningful. Currently all that's tested
are simple commands. Not the main functionality namely the actual
streaming of changes.
I wonder if somebody has a great idea for cancelling pg_recvlogical
after a while. Right now my best idea is to add a new
--stop-after-messages parameter. Does anybody have a better idea?
If that's the way, would somebody object to tests and the parameter
being added now? The potential harm seems pretty low and the additional
tests would cover the walsender interface that's not covered by any
tests right now...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Nelson | 2014-05-15 21:27:36 | CTE that result in repeated sorting of the data |
Previous Message | Andres Freund | 2014-05-15 20:58:20 | Re: Logical replication woes |