| From: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Fujii Masao' <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com" <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com>, "zyu(at)yugabyte(dot)com" <zyu(at)yugabyte(dot)com> |
| Subject: | RE: [Proposal] Add foreign-server health checks infrastructure |
| Date: | 2022-03-04 06:17:26 |
| Message-ID: | TYAPR01MB5866982FC21ABE5DF3C1E3A2F5059@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Hackers,
> It's not happy, but I'm not sure about a good solution. I made a timer reschedule
> if connection lost had detected. But if queries in the transaction are quite short,
> catching SIGINT may be fail.
Attached uses another way: sets pending flags again if DoingCommandRead is true.
If a remote server goes down while it is in idle_in_transaction,
next query will fail because of ereport(ERROR).
How do you think?
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v14_0001_expose_cancel_message.patch | application/octet-stream | 1.8 KB |
| v14_0002_add_health_check.patch | application/octet-stream | 7.0 KB |
| v14_0003_add_doc.patch | application/octet-stream | 1.4 KB |
| v14_0004_add_test.zip | application/x-zip-compressed | 843 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2022-03-04 06:21:41 | Re: Add the replication origin name and commit-LSN to logical replication worker errcontext |
| Previous Message | osumi.takamichi@fujitsu.com | 2022-03-04 06:15:49 | RE: Add the replication origin name and commit-LSN to logical replication worker errcontext |