| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | shveta malik <shveta(dot)malik(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: sequencesync worker race with REFRESH SEQUENCES |
| Date: | 2026-07-21 05:18:32 |
| Message-ID: | OS9PR01MB12149C627BC08380711F51F29F5C22@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Amit, Vignesh,
> I agree with this reasoning for not performing connection before
> checking sequences.
My assumption was that the connection was not so heavy operation.
If it's not correct, yes the connection should be established later.
> However, I feel changing the
> connection string shouldn't be performed often enough to worry about
> or adding additional complexity in code or adding more optimizations
> for it.
I suspect this part rarely happens. So Ok for me not to spend hacking costs.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-07-21 05:34:23 | Re: sequencesync worker race with REFRESH SEQUENCES |
| Previous Message | Ian Lawrence Barwick | 2026-07-21 05:14:53 | Re: [PATCH] Add pg_get_event_trigger_ddl() function |