From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: vacuum analyze after updating from CVS? |
Date: | 2003-07-20 19:14:08 |
Message-ID: | 20030720191408.GA25028@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Jul 13, 2003 at 11:12:21 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> > It would be easy to show you the explain analyze output before
> > the rebuild, the explain analyze after the rebuild and explain
> > analyze after the vacuum analyze.
> > What else would be useful to see?
>
> The contents of pg_stats for the table(s) involved, before and after,
> might be interesting too.
>
> regards, tom lane
I didn't see the effect on my latest upgrade. I will keep watching (dumping
pg_stats just before upgrading) for this for a while and see if it happens
again.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-07-20 19:28:05 | Re: Avoid the interpretation of \n in the psql output |
Previous Message | Bruce Momjian | 2003-07-20 18:32:14 | Re: Q: Executing functions at connect/disconnect? |