From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Truly bizarre behavior with VACUUM FULL?
Date: Fri, 18 Apr 2003 21:54:25 -0400
Message-ID: <18731.1050717265@sss.pgh.pa.us> (raw)
In-Reply-To: <200304181849.03273.josh@agliodbs.com>
References: <200304181525.59152.josh@agliodbs.com>
<17325.1050711213@sss.pgh.pa.us>
<200304181849.03273.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
>> What is causing the new improved version to come back again? Are you
>> doing another manual CREATE OR REPLACE each day? How exactly?
> Manual CREATE OR REPLACE, yes. And then I test it. And it works for the
> rest of the day ...
So try a VACUUM FULL right after you fix it, instead of waiting for the
cron job to fire.
My bet is that there is something else being done by your nightly script
that is restoring the old definition.
regards, tom lane
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: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Truly bizarre behavior with VACUUM FULL?
In-Reply-To: <18731.1050717265@sss.pgh.pa.us>
* 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