| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Euler Taveira' <euler(at)eulerto(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | RE: speed up a logical replica setup |
| Date: | 2024-07-30 08:37:38 |
| Message-ID: | TYAPR01MB569224B53ED1A53284710C4BF5B02@TYAPR01MB5692.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Euler,
I applied your patch and confirmed it could fix the issue [1].
METHOD
=======
1. shortened the snapshot interval to 3ms, and
```
-#define LOG_SNAPSHOT_INTERVAL_MS 15000
+#define LOG_SNAPSHOT_INTERVAL_MS 3
```
2. ran test 040_pg_createsubscriber.pl many times.
Before patching, I could reproduce the failure when I ran less than 1hr.
After patching, I ran more than 1hr but I could not reproduce.
Since this is a timing issue which I could not surely reproduce, I wanted others
to test it as well.
[1]: https://www.postgresql.org/message-id/68de6498-0449-a113-dd03-e198dded0bac%40gmail.com
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2024-07-30 08:41:40 | Re: Conflict detection and logging in logical replication |
| Previous Message | David Rowley | 2024-07-30 08:22:42 | Re: COPY FROM crash |