From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Add client connection check during the execution of the query |
Date: | 2019-07-05 06:02:44 |
Message-ID: | CA+hUKGLuJtjjwYRk80w168zpbUcqSGU8PVvkBGpj75Kain2Veg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 5, 2019 at 5:36 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Sat, Feb 9, 2019 at 6:16 AM <s(dot)cherkashin(at)postgrespro(dot)ru> wrote:
> > The purpose of this patch is to stop the execution of continuous
> > requests in case of a disconnection from the client. In most cases, the
> > client must wait for a response from the server before sending new data
> > - which means there should not remain unread data on the socket and we
> > will be able to determine a broken connection.
> > Perhaps exceptions are possible, but I could not think of such a use
> > case (except COPY). I would be grateful if someone could offer such
> > cases or their solutions.
> > I added a test for the GUC variable when the client connects via SSL,
> > but I'm not sure that this test is really necessary.
>
> [review]
Email to Sergey is bouncing back. I've set this to "Waiting on
author" in the Commitfest app.
--
Thomas Munro
https://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2019-07-05 06:28:14 | Re: Add client connection check during the execution of the query |
Previous Message | Pavel Stehule | 2019-07-05 05:58:21 | Re: range_agg |