X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id C5688475E4D
	for <pgsql-sql@postgresql.org>; Fri, 18 Apr 2003 18:26:17 -0400 (EDT)
Received: from davinci.ethosmedia.com (unknown [209.10.40.251])
	by postgresql.org (Postfix) with ESMTP id 1DF34475458
	for <pgsql-sql@postgresql.org>; Fri, 18 Apr 2003 18:26:17 -0400 (EDT)
Received: from [66.219.92.2] (HELO temoku)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 2973521 for pgsql-sql@postgresql.org;
	Fri, 18 Apr 2003 15:26:15 -0700
Content-Type: text/plain;
  charset="us-ascii"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-sql@postgresql.org
Subject: Truly bizarre behavior with VACUUM FULL?
Date: Fri, 18 Apr 2003 15:25:59 -0700
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200304181525.59152.josh@agliodbs.com>
X-Spam-Status: No, hits=-13.0 required=5.0 tests=BAYES_01,USER_AGENT_KMAIL
	autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200304/291
X-Sequence-Number: 12992

Folks,

I have a system on a 7.2.4 database.  Let me tell you what appears to be=20
happening:

I have a bug-fixed version of a function, which replaced a buggy version of=
=20
the function via CREATE OR REPLACE.  Each night, when the database goes=20
through VACUUM FULL, the old (buggy) version of the function seems to=20
overwrite the new (correct) version of the function.

Is it possible that VACUUM FULL is restoring the discarded tuple in the sys=
tem=20
table and dropping the valid one?

I can think of ways to fix this bizarre behavior, but thought that someone=
=20
might want to look at it first.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco