From: Josh Berkus <josh@agliodbs.com>
To: pgsql-sql@postgresql.org
Subject: Truly bizarre behavior with VACUUM FULL?
Date: Fri, 18 Apr 2003 15:25:59 -0700
Message-ID: <200304181525.59152.josh@agliodbs.com> (raw)
Folks,
I have a system on a 7.2.4 database. Let me tell you what appears to be
happening:
I have a bug-fixed version of a function, which replaced a buggy version of
the function via CREATE OR REPLACE. Each night, when the database goes
through VACUUM FULL, the old (buggy) version of the function seems to
overwrite the new (correct) version of the function.
Is it possible that VACUUM FULL is restoring the discarded tuple in the system
table and dropping the valid one?
I can think of ways to fix this bizarre behavior, but thought that someone
might want to look at it first.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: Truly bizarre behavior with VACUUM FULL?
In-Reply-To: <200304181525.59152.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox