Re: psql swallowed my "BEGIN;" on reset... user beware?

From: Ryan Kelly <rpkelly22(at)gmail(dot)com>
To: Moshe Jacobson <moshe(at)neadwerx(dot)com>
Cc: Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: psql swallowed my "BEGIN;" on reset... user beware?
Date: 2013-09-30 16:18:36
Message-ID: 20130930161836.GB16574@llserver.lakeliving.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Sep 09/30/13, 2013 at 11:49:29AM -0400, Moshe Jacobson wrote:
> On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> wrote:
>
> > After restarting the server in another window, I was surprised that my
> > command did not run in a transaction:
> >
> > spc_test_scratch=# BEGIN; DROP VIEW IF EXISTS ptest_mip ; DROP VIEW
> > rent_info; \i create.view.rent_info.sql
> > FATAL: terminating connection due to administrator command
> > server closed the connection unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
> > The connection to the server was lost. Attempting reset: Succeeded.
> > NOTICE: view "ptest_mip" does not exist, skipping
> > DROP VIEW
> > DROP VIEW
> > CREATE VIEW
> > spc_test_scratch=# commit;
> > WARNING: there is no transaction in progress
> > COMMIT
> >
>
> This seems like a pretty serious issue. My opinion is that psql should
> refuse to execute further commands on a line of input if any of them fails
> due to a terminated connection.

Err, meant SendQuery and PSQLexec in my last mail. Not sure how I typed
ProcessResult twice...

-Ryan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Gilberto Castillo 2013-09-30 16:25:29 Re: [pgsql-es-ayuda] Fwd: Help on ṕerformance
Previous Message Carlos Eduardo Sotelo Pinto 2013-09-30 16:16:33 Re: [pgsql-es-ayuda] Fwd: Help on ṕerformance