| From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
|---|---|
| To: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Improve the connection failure error messages |
| Date: | 2024-01-31 22:12:59 |
| Message-ID: | CAHut+PvQFJ51xhAwi==nW_5z4Q386oE9VhKO0a2K6RWBD+9MpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 31, 2024 at 9:58 PM Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> wrote:
>
>
>> AFAIK some recent commits patches (e,g [1] for the "slot sync"
>> development) have created some more cases of "could not connect..."
>> messages. So, you might need to enhance your patch to deal with any
>> new ones in the latest HEAD.
>>
>> ======
>> [1] https://github.com/postgres/postgres/commit/776621a5e4796fa214b6b29a7ca134f6c138572a
>>
> Thank you for the update.
> The v3 patch has the changes needed as per the latest HEAD.
>
Hi, just going by visual inspection of the v2/v3 patch diffs, the
latest v3 LGTM.
======
Kind Regards,
Peter Smith.
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-01-31 22:28:25 | Re: libpq fails to build with TSAN |
| Previous Message | Robert Haas | 2024-01-31 21:36:09 | Re: Add system identifier to backup manifest |