Re: Rollback on include error in psql

From: Viktor Shitkovskiy <hanksmail(at)gmail(dot)com>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Rollback on include error in psql
Date: 2014-12-29 07:28:01
Message-ID: CAK7FUCwa4++RzW7y0chFm+0tdZS4dzgwE8GWhfjStooqatmfeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

So should I report a bug somewhere?

As a workaround I'm currently using a wrapper bash script that parses the
source psql script and checks if the 'include' and 'copy-from' files do
really exist.

On Mon, Dec 29, 2014 at 4:04 AM, David G Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> I would suggest an enhancement whereby psql will send a guaranteed-to-fail
> command to the server upon failing to find an included file - at least in
> non-interactive mode; in interactive mode the warning is likely sufficient
> though the interplay with auto-commit would be concerning.
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/Rollback-on-include-error-in-psql-tp5832192p5832233.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2014-12-29 09:38:12 Re: BUG #12292: index row size 1480 exceeds maximum 1352 for index
Previous Message Sandeep Thakkar 2014-12-29 06:30:46 Re: BUG #12328: can't install the postgresql

Browse pgsql-general by date

  From Date Subject
Next Message sramay 2014-12-29 12:42:18 vacuum vs pg_repack vs pg_reorg
Previous Message David G Johnston 2014-12-29 01:04:04 Re: Rollback on include error in psql