Re: psql swallowed my "BEGIN;" on reset... user beware?
От | Moshe Jacobson |
---|---|
Тема | Re: psql swallowed my "BEGIN;" on reset... user beware? |
Дата | |
Msg-id | CAJ4CxLmnWrVK8Fw5XsXdC1nQu9+zQw9VHaYhU-VBRs5MqD98PA@mail.gmail.com обсуждение исходный текст |
Ответ на | psql swallowed my "BEGIN;" on reset... user beware? (Ken Tanzer <ken.tanzer@gmail.com>) |
Ответы |
Re: psql swallowed my "BEGIN;" on reset... user beware?
Re: psql swallowed my "BEGIN;" on reset... user beware? Re: psql swallowed my "BEGIN;" on reset... user beware? |
Список | pgsql-general |
On Sun, Sep 29, 2013 at 2:18 AM, Ken Tanzer <ken.tanzer@gmail.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.sqlFATAL: terminating connection due to administrator commandserver closed the connection unexpectedlyThis probably means the server terminated abnormallybefore or while processing the request.The connection to the server was lost. Attempting reset: Succeeded.NOTICE: view "ptest_mip" does not exist, skippingDROP VIEWDROP VIEWCREATE VIEWspc_test_scratch=# commit;WARNING: there is no transaction in progressCOMMIT
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
Nead Werx, Inc. | Manager of Systems Engineering
2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
moshe@neadwerx.com | www.neadwerx.com
moshe@neadwerx.com | www.neadwerx.com
"Quality is not an act, it is a habit." -- Aristotle
В списке pgsql-general по дате отправления: