| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Markus Schiltknecht <markus(at)bluegap(dot)ch>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: InitPostgres and flatfiles question |
| Date: | 2007-01-05 03:25:05 |
| Message-ID: | 200701050325.l053P5X13691@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Markus Schiltknecht <markus(at)bluegap(dot)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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | markwkm | 2007-01-05 03:25:41 | Re: ideas for auto-processing patches |
| Previous Message | Gavin Sherry | 2007-01-05 02:44:56 | Re: ideas for auto-processing patches |