Re: InitPostgres and flatfiles question - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: InitPostgres and flatfiles question
Date
Msg-id 200701050325.l053P5X13691@momjian.us
Whole thread Raw
In response to Re: InitPostgres and flatfiles question  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: InitPostgres and flatfiles question  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Markus Schiltknecht <markus@bluegap.ch> writes:
> > Tom Lane wrote:
> >> Hm, that's an interesting point.  psql's -c just shoves its whole
> >> argument string at the backend in one PQexec(), instead of dividing
> >> at semicolons as psql does with normal input.
> 
> > Is there a good reason to not let psql -c behave exactly like psql from 
> > STDIN?
> 
> Backwards compatibility, mostly --- there seems to be a considerable
> risk of subtly breaking people's scripts if we change the transactional
> boundaries for psql -c commands.

True, but if we keep hitting people who don't expect this behavior, I
wonder if we should just fix it and mention it in the release notes.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: ideas for auto-processing patches
Next
From: markwkm@gmail.com
Date:
Subject: Re: ideas for auto-processing patches