I upgraded to 7.4.3 this morning and did a vacuum full analyze on the
problem table and now the indexes show the correct number of records
Josh Berkus <josh(at)agliodbs(dot)com>
Sent by: pgsql-performance-owner(at)postgresql(dot)org
09/21/04 10:49 AM
"Patrick Hatcher" <pathat(at)comcast(dot)net>
"Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>,
Re: [PERFORM] vacuum full & max_fsm_pages question
> Sorry. I wrote PG 7.4.2 and then I erased it to write something else
> then forgot to add it back.
Odd. You shouldn't be having to re-vacuum on 7.4.
> And thanks for the Page info. I was getting frustrated and looked in
> wrong place.
> So it's probably best to drop and readd the indexes then?
Well, I have to wonder if you've not run afoul of the known 7.4.2 bug
regarding indexes. This system hasn't had an improper database shutdown
power-out in the last few weeks, has it?
Aglio Database Solutions
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
In response to
pgsql-performance by date
|Next:||From: Jason Coene||Date: 2004-09-23 16:53:25|
|Subject: Re: Caching of Queries|
|Previous:||From: Mr Pink||Date: 2004-09-23 15:39:31|
|Subject: Re: SAN performance|