Re: Danger of automatic connection reset in psql

From: Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Danger of automatic connection reset in psql
Date: 2016-10-20 11:55:47
Message-ID: CACACo5TLTOiZ6_sTpnE-M=pj_uKETV6LWKZyZoaAa0mB63M+tw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 20, 2016 at 12:28 PM, Oleksandr Shulgin <
oleksandr(dot)shulgin(at)zalando(dot)de> wrote:

>
> Since this is already an improvement, I'm attaching a patch.
>
> If on the other hand, someone is pasting into psql's terminal a block of
> commands enclosed in BEGIN/COMMIT, the same bug is triggered: BEGIN doesn't
> have effect and the rest of commands run outside of transaction.
>
> Is it possible at all to protect against the latter case? How?
>

One idea I was just suggested is to make interactive psql sessions buffer
in all available input, before it's going to block. This way it doesn't
matter if the multiple statements are appearing on one line or are being
pasted.

Feasible?

--
Alex

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-10-20 12:29:37 Re: Indirect indexes
Previous Message Oleksandr Shulgin 2016-10-20 10:48:24 Re: Danger of automatic connection reset in psql