On Mon, Jun 02, 2003 at 03:14:33PM -0400, Bruce Momjian wrote:
>
> Oh, yes, sorry, I was confusing psql -c and -f. -c is clearly different.
But if -f follows the ~/.psqlrc variable, then you'll definitively will
have to put back the "SET AUTOCOMMIT to off" to scripts... (vacuumdb and
clusterdb s
Bruce Momjian <[EMAIL PROTECTED]> writes:
> In thinking about it, I don't see how we can ignore .psqlrc if it has
> autocommit set to off. Imagine I am in psql and I do '\i file', and it
> works, so I code up psql -c in a script, and it doesn't work --- would
> be quite strange.
What's your point
Bruce Momjian <[EMAIL PROTECTED]> 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 explici
Oh, yes, sorry, I was confusing psql -c and -f. -c is clearly different.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Yeah, it's a bit warty, but psql -c is inherently different f
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > In thinking about it, I don't see how we can ignore .psqlrc if it has
> > autocommit set to off. Imagine I am in psql and I do '\i file', and it
> > works, so I code up psql -c in a script, and it doesn't work --- would
> > be quite s
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > SET autocommit to 'off' is going away in 7.4 so the SET USER command
> > will not work anymore in that release, and I can't think of a
> > workaround. There will be interface-specific settings, I assume, but I
> > am not sure how that
SET autocommit to 'off' is going away in 7.4 so the SET USER command
will not work anymore in that release, and I can't think of a
workaround. There will be interface-specific settings, I assume, but I
am not sure how that would be controlled per-user.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > SET autocommit to 'off' is going away in 7.4 so the SET USER command
> > will not work anymore in that release, and I can't think of a
> > workaround. There will be interface-specific settings, I assume, but I
> > am not sure how that
Bruce Momjian <[EMAIL PROTECTED]> writes:
> SET autocommit to 'off' is going away in 7.4 so the SET USER command
> will not work anymore in that release, and I can't think of a
> workaround. There will be interface-specific settings, I assume, but I
> am not sure how that would be controlled per-u
On Sun, 1 Jun 2003, Rasmus Resen Amossen wrote:
> >We have been there, done that, and decided it was a bad idea. I suggest
> >you do a little reading in the mail list archives.
>
> I have searched the lists archives for the words "commit", "autocommit" and
> "transaction" but couldn't find any
We have been there, done that, and decided it was a bad idea. I suggest
you do a little reading in the mail list archives.
I have searched the lists archives for the words "commit", "autocommit" and
"transaction" but couldn't find any discussion on wheter to give a database
administrator the opt
"Rasmus Resen Amossen" <[EMAIL PROTECTED]> writes:
> Therefor: Are there any plans to give the administrator an OPTION to turn
> the behavior off through a parameter "autocommit = " in the config
> file?
We have been there, done that, and decided it was a bad idea. I suggest
you do a little rea
I'm not sure that this is the right list to ask - but after having googled a
while it seems that the only ones that might be able to answer this question
is the developers. Therefor, here we go:
As far as I have understood, postgres is autocommiting each typed statement
UNLESS the user remembe
13 matches
Mail list logo
