Josh Berkus wrote:
> I just encountered a very interesting bug in ver 7.2.1.
> As an experiment, I tried running a VACCUUM ANALYZE on a table inside a
> Function after the function had made a large number of updates to that
> table. I assumed that this wouldn't work, but I thought I'd give it a
> It did not work. What it did was interesting.
> Postgres terminated my back-end connection to the server when it
> reached the VACUUM statement.
> Next, I reconnected. I was quite surprised to discover that Postgres
> had *not* rolled back the changes made by the function before it
> I'm testing to see if I can reproduce this issue on 7.3b1. I'll
> e-mail you with a test database if I can.
You will not be able to reproduce it. 7.3 disabled VACUUM inside
functions for that exact reason.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-bugs by date
|Next:||From: Matthew Wakeling||Date: 2002-10-04 16:47:16|
|Subject: Possible bug in PostgreSQL query planner|
|Previous:||From: Ruslan A Dautkhanov||Date: 2002-10-03 10:38:00|
|Subject: 7.2.1: Can't create prcedural language PLPERL|