Re: ERROR: REINDEX DATABASE: Can be executed only on the currently open database.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Clodoaldo Pinto Neto <clodoaldo_pinto(at)yahoo(dot)com(dot)br>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ERROR: REINDEX DATABASE: Can be executed only on the currently open database.
Date: 2004-04-12 03:44:03
Message-ID: 28976.1081741443@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?iso-8859-1?q?Clodoaldo=20Pinto=20Neto?= <clodoaldo_pinto(at)yahoo(dot)com(dot)br> writes:
> --- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu: >
>> It's fairly unlikely that that is the solution you need. How often do
>> you vacuum this table?

> A vacuum is executed every tree hours to the whole database after it is updated
> with more than 300.000 inserts and deletes.

And is that *sufficient*? Is the table size staying constant, or
growing? It seems likely to me that you have an increasing amount
of wasted space in the table, and that the real solution requires
more frequent vacuums and/or increased FSM settings.

What does "vacuum verbose" have to say about the table?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Edmund Dengler 2004-04-12 03:45:50 Re: REINDEX slow?
Previous Message Hitesh Bagadiya 2004-04-12 03:43:52 Re: Sorting in Unicode not working