From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug in Function-Transactions? |
Date: | 2002-10-04 16:05:04 |
Message-ID: | 200210041605.g94G54b09038@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Josh Berkus wrote:
> Folks,
>
> 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
> try.
>
> 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
> crashed.
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Wakeling | 2002-10-04 16:47:16 | Possible bug in PostgreSQL query planner |
Previous Message | Ruslan A Dautkhanov | 2002-10-03 10:38:00 | 7.2.1: Can't create prcedural language PLPERL |