| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: BF member drongo doesn't like 035_standby_logical_decoding.pl |
| Date: | 2025-01-24 19:56:45 |
| Message-ID: | 520687.1737748605@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alexander Lakhin <exclusion(at)gmail(dot)com> writes:
> There is also a reference to a discussion of the failure there:
> https://www.postgresql.org/message-id/657815a2-5a89-fcc1-1c9d-d77a6986bc26@gmail.com
> (In short, I observed that that test suffers from bgwriter's activity.)
Hmm, that's an interesting theory, but it fails to explain why
only drongo is showing this failure. It's not particularly slow
compared to some other BF animals.
I suspect the correct explanation involves "it's Windows" somehow,
but no idea exactly how.
BTW, looking more closely at the failures, I notice that some of them
are 'with vacuum on pg_authid' but others are 'with vacuum on pg_class'.
So those are two different steps in the test script, and there are
other steps that are very similar but have not failed. Curiouser
and curiouser.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Jones | 2025-01-24 19:59:11 | Re: XMLDocument (SQL/XML X030) |
| Previous Message | Andres Freund | 2025-01-24 19:52:20 | Re: BF member drongo doesn't like 035_standby_logical_decoding.pl |