Re: [HACKERS] interesting side effect of autocommit = off

2002-10-14 Thread Joe Conway
Tom Lane wrote: > Yeah, and libpq does one too in some cases :-(. Both of these need to > be fixed before 7.3 if possible. > > Whether we fix these or not, it'd be a good idea to document that > turning autocommit off in postgresql.conf is not yet well-supported. > I doubt that all client-side c

Re: [HACKERS] interesting side effect of autocommit = off

2002-10-14 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > I am sure the problem is that psql doing a query on startup: Yeah, and libpq does one too in some cases :-(. Both of these need to be fixed before 7.3 if possible. Whether we fix these or not, it'd be a good idea to document that turning autocommit of

Re: [HACKERS] interesting side effect of autocommit = off

2002-10-14 Thread Bruce Momjian
Barry Lind wrote: > After turning autocommit off on my test database, my cron scripts that > vacuum the database are now failing. > > This can be easily reproduced, turn autocommit off in your > postgresql.conf, then launch psql and run a vacuum. > > [blind@blind databases]$ psql files > Welco

[HACKERS] interesting side effect of autocommit = off

2002-10-14 Thread Barry Lind
After turning autocommit off on my test database, my cron scripts that vacuum the database are now failing. This can be easily reproduced, turn autocommit off in your postgresql.conf, then launch psql and run a vacuum. [blind@blind databases]$ psql files Welcome to psql 7.3b2, the PostgreSQL i