Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Continue transactions after errors in psql

From: John DeSoi <desoi(at)pgedit(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org, Michael Paesold <mpaesold(at)gmx(dot)at>,Greg Sabino Mullane <greg(at)turnstep(dot)com>,pgsql-hackers(at)postgresql(dot)org, Richard Huxton <dev(at)archonet(dot)com>
Subject: Re: [HACKERS] Continue transactions after errors in psql
Date: 2005-04-27 00:02:30
Message-ID: (view raw or whole thread)
Lists: pgsql-hackerspgsql-patches
On Apr 26, 2005, at 10:35 AM, Tom Lane wrote:

> Once you've got such an infrastructure, it makes sense to allow an
> interactive mode that automatically puts such things around each
> statement.  But I can't really see the argument for using such a
> behavior in a script.  Scripts are too stupid.

Would it be possible to have a command line switch and/or a psql 
variable to control "interactive"? If I recall correctly, the setting 
depends on tty and there are possible interactive uses of psql outside 
of a terminal session. With so many things depending on this, it would 
be nice to be able to override the default.


John DeSoi, Ph.D.
Power Tools for PostgreSQL

In response to

pgsql-hackers by date

Next:From: Jan WieckDate: 2005-04-27 00:02:43
Subject: Re: DO INSTEAD and conditional rules
Previous:From: Greg StarkDate: 2005-04-26 23:28:21
Subject: Re: [PERFORM] Bad n_distinct estimation; hacks suggested?

pgsql-patches by date

Next:From: Tom LaneDate: 2005-04-27 03:15:21
Subject: Re: Cleaning up unreferenced table files
Previous:From: Heikki LinnakangasDate: 2005-04-26 22:18:12
Subject: Re: Cleaning up unreferenced table files

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group