From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
---|---|
To: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql swallowed my "BEGIN;" on reset... user beware? |
Date: | 2013-09-30 15:49:29 |
Message-ID: | CAJ4CxLmnWrVK8Fw5XsXdC1nQu9+zQw9VHaYhU-VBRs5MqD98PA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
Moshe Jacobson
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
moshe(at)neadwerx(dot)com | www.neadwerx.com
"Quality is not an act, it is a habit." -- Aristotle
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2013-09-30 16:06:55 | Re: psql swallowed my "BEGIN;" on reset... user beware? |
Previous Message | Hellmuth Vargas | 2013-09-30 15:36:14 | Re: [pgsql-es-ayuda] Re: [pgsql-es-ayuda] Fwd: Help on ṕerformance |