| From: | Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication |
| Date: | 2026-01-09 15:53:55 |
| Message-ID: | 89850524-a014-46cf-ab20-0f3961dd566c@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Fujii,
On 07/01/2026 03:36, Fujii Masao wrote:
> This approach may be somewhat unstable. If there's a more robust
> way to terminate pg_recvlogical on Windows, I'd be happy to switch
> to it, but I couldn't come up with a better option.
Thanks for the updated patch set!
I applied them and it builds correctly and the test passes on my laptop.
About termination on Windows, I've noticed the following in file
006_logical_decoding.pl:
> # some Windows Perls at least don't like IPC::Run's start/kill_kill regime.
> skip "Test fails on Windows perl", 2 if $Config{osname} eq 'MSWin32';
It seems that previously, in a similar situation the decision was to
skip it on Windows.
If we adopt the same approach for this test it should be fine, the
production code in the patch is not Windows-specific.
Alternatively if we keep the approach in v4, we can consider
updating 006_logical_decoding.pl as well so they're consistent.
What do you think?
--
Thanks,
Mircea Cadariu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-01-09 16:04:58 | Re: Unstable isolation timeouts regression test on NetBSD? |
| Previous Message | Henson Choi | 2026-01-09 15:44:31 | Re: SQL Property Graph Queries (SQL/PGQ) |