Skip site navigation (1) Skip section navigation (2)

Re: drop tempoary table VERY slow

From: Andrew McMillan <andrew(at)catalyst(dot)net(dot)nz>
To: Sam Liddicott <sam(dot)liddicott(at)ananova(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: drop tempoary table VERY slow
Date: 2002-06-06 10:52:06
Message-ID: (view raw or whole thread)
Lists: pgsql-bugs
On Thu, 2002-06-06 at 01:54, Sam Liddicott wrote:

> > 
> > It would be interesting to see the 'vacuum full analyze' 
> > results for the
> > system tables in that DB, although perhaps less interesting while you
> > are running your current solution - maybe a comparison would be
> > worthwhile.
> Alas we won't be able to downgrade as it affected the service seriously.
> In doing a full vacuum I notice such errors as:
> NOTICE:  Index pg_index_indrelid_index NUMBER OF INDEX' TUPLES (92) IS NOT
> THE SAME AS HEAP' (86). Recreate the index
> Hmm.  It's not my index (of course) I'm not sure how to go about re-creating
> it.

To reindex the system tables you need to shut down your database, then
run a standalone postgres backend:

postgres -O -P <dbname>

Inside that you then:


Once it is done, quit and restart your database.

Andrew @ Catalyst .Net.NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB:        PHYS: Level 2, 150-154 Willis St
DDI: +64(4)916-7201    MOB: +64(21)635-694    OFFICE: +64(4)499-2267
       Are you enrolled at yet?

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2002-06-06 11:56:57
Subject: Bug #683: pg_dump don't works with 1500 tables
Previous:From: Bruce MomjianDate: 2002-06-05 17:57:29
Subject: Re: [Fwd: Bug#146689: postgresql-client: 'GRANT DELETE' autocompletion

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group