From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Subject: | Re: failures in t/031_recovery_conflict.pl on CI |
Date: | 2022-04-29 23:26:59 |
Message-ID: | 465685.1651274819@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Questions:
> - I'm planning to backpatch the test as 031_recovery_conflict.pl, even though
> preceding numbers are unused. It seems way more problematic to use a
> different number in the backbranches than have gaps?
+1
> - The test uses pump_until() and wait_for_log(), which don't exist in the
> backbranches. For now I've just inlined the implementation, but I guess we
> could also backpatch their introduction?
I'd backpatch --- seems unlikely this will be the last need for 'em.
> pgindent uses some crazy formatting nearby:
> SendRecoveryConflictWithBufferPin(
> PROCSIG_RECOVERY_CONFLICT_STARTUP_DEADLOCK);
I do not believe that that line break is pgindent's fault.
If you just fold it into one line it should stay that way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-04-30 01:20:05 | Re: bogus: logical replication rows/cols combinations |
Previous Message | Tomas Vondra | 2022-04-29 20:31:59 | Re: bogus: logical replication rows/cols combinations |