X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 3B135475B85
	for <pgsql-sql@postgresql.org>; Fri, 18 Apr 2003 21:54:23 -0400 (EDT)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP id 82E004758C9
	for <pgsql-sql@postgresql.org>; Fri, 18 Apr 2003 21:54:22 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3J1sPU6018732;
	Fri, 18 Apr 2003 21:54:25 -0400 (EDT)
To: josh@agliodbs.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Truly bizarre behavior with VACUUM FULL? 
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>
Comments: In-reply-to Josh Berkus <josh@agliodbs.com>
	message dated "Fri, 18 Apr 2003 18:49:03 -0700"
Date: Fri, 18 Apr 2003 21:54:25 -0400
Message-ID: <18731.1050717265@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Spam-Status: No, hits=-32.3 required=5.0
	tests=BAYES_00,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	REFERENCES,REPLY_WITH_QUOTES 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/294
X-Sequence-Number: 12995

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