Re: Conflict detection for multiple_unique_conflicts in logical replication

Hi, For v3, CFbot failed for the patch test case due to unstable test steps. Truncating the subscriber table resolved the apply worker error but sometimes caused out-of-order inserts, leading to unexpected failures instead of a conflict error. Fixed this and updated the LOG regex check to avoid fa

Re: Selectively invalidate caches in pgoutput module

On Wed, Mar 12, 2025 at 5:46 PM Hayato Kuroda (Fujitsu) wrote: > > > Thanks, the patch looks mostly good to me. I have made few cosmetic > > changes in the attached and combined both the patches. > > Thanks, it looks good to me. > > > The existing > > Alter Publication ... Rename tests don't test

Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options

On Sun, 9 Mar 2025, 20:07 Oliver Ford, wrote: > On Sun, Mar 9, 2025 at 6:40 AM Tatsuo Ishii wrote: > >> > Attached version removes the non-nulls array. That seems to speed >> > everything up. Running the above query with 1 million rows averages >> 450ms, >> > similar when using lead/lag. >> >>

Fwd: [BUG]: the walsender does not update its IO statistics until it exits

Forgot to cc... -- Forwarded message - 发件人： Xuneng Zhou Date: 2025年3月13日周四 19:15 Subject: Re: [BUG]: the walsender does not update its IO statistics until it exits To: Bertrand Drouvot Hi, Thanks for working on this! I'm glad to see that the patch ( https://www.postgresql.org/

Fwd: [BUG]: the walsender does not update its IO statistics until it exits

Sorry, forgot to cc this one too. -- Forwarded message - 发件人： Xuneng Zhou Date: 2025年3月13日周四 19:29 Subject: Re: [BUG]: the walsender does not update its IO statistics until it exits To: Bertrand Drouvot Hi, Given that PGSTAT_MIN_INTERVAL is the go-to setting for stats flushes

<    1   2