From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | Kevin Hale Boyes <kcboyes(at)gmail(dot)com>, Kartyshov Ivan <i(dot)kartyshov(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, hlinnaka(at)iki(dot)fi, alvherre(at)alvh(dot)no-ip(dot)org, pashkin(dot)elfe(at)gmail(dot)com, bharath(dot)rupireddyforpostgres(at)gmail(dot)com, euler(at)eulerto(dot)com, thomas(dot)munro(at)gmail(dot)com, peter(at)eisentraut(dot)org, amit(dot)kapila16(at)gmail(dot)com, dilipbalaut(at)gmail(dot)com, smithpb2250(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [HACKERS] make async slave to wait for lsn to be replayed |
Date: | 2024-09-17 09:00:00 |
Message-ID: | 88a394be-ebfe-0a3d-f2ac-15f9ce41960d@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
17.09.2024 10:47, Alexander Korotkov wrote:
> Yes, now I did reproduce. I got that the problem could be that insert
> LSN is not yet written at primary, thus wait_for_catchup doesn't wait
> for it. I've workarounded that using pg_switch_wal(). The revised
> patchset is attached.
Thank you for the revised patch!
The improved test works reliably for me (100 out of 100 runs passed),
Best regards,
Alexander
From | Date | Subject | |
---|---|---|---|
Next Message | Corey Huinker | 2024-09-17 09:02:49 | Re: Statistics Import and Export |
Previous Message | wenhui qiu | 2024-09-17 08:48:16 | Re: Can we rely on the ordering of paths in pathlist? |