On 2012-06-19, Rafal Pietrak <rafal@xxxxxxxxxxxxxxxxxx> wrote: > And we are talking about interractive psql breaking transaction because > of syntax error - almost always this is a one time typo. I'd prefere it > to be a bit more "sloopy", then deployed SQL application (e.g. > non-interactive session). possibly you could program keyboard macros to handle savepoints to have an easy way to recover from these errors, but if you're working on a busy database keeping a transaction open whislt you think about syntax is going to cost perfromance for the other users. -- ⚂⚃ 100% natural -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
