Re: Postgres config file: autocommit = off - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Postgres config file: autocommit = off
Date
Msg-id 200306021914.h52JEXm20625@candle.pha.pa.us
Whole thread Raw
In response to Re: Postgres config file: autocommit = off  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Oh, yes, sorry, I was confusing psql -c and -f.  -c is clearly different.

---------------------------------------------------------------------------

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Yeah, it's a bit warty, but psql -c is inherently different from a psql
> >> script.  IMHO it's not reasonable to make (shell) scripts using psql -c
> 
> > How is it different, except for having no prompt?
> 
> It's different because it's explicitly designed for convenient execution
> of a single command.  Thus, autocommit off would be useless and
> counterproductive.  Also, since the -c string is fed to PQexec as a
> single query (again different from the psql stdin behavior), if you do
> put multiple commands into -c then you get them executed as a single
> transaction anyway.  So you do not need or want .psqlrc modifying the
> behavior in either case.
> 
> One of the reasons for taking autocommit control out of the backend and
> pushing it up to the client level is exactly to make it feasible to take
> these sorts of application-level considerations into account when
> choosing the behavior.
> 
>             regards, tom lane
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres config file: autocommit = off
Next
From: Tom Lane
Date:
Subject: Re: initdb problems handling super username with spaces.