From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Philipp Marek <philipp(dot)marek(at)emerion(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Btree indizes, FILLFACTOR, vacuum_freeze_min_age and CLUSTER |
Date: | 2009-05-13 17:52:45 |
Message-ID: | 20090513175245.GE5986@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Philipp Marek wrote:
> Hello everybody,
>
> we're using postgresql 8.3 for some logging framework.
>
> There are several tables for each day (which are inherited from a common
> base), which
> - are filled during the day,
> - after midnight the indizes are changed to FILLFACTOR=100, and
> - the tables get CLUSTERed by the most important index.
> - Some time much later the tables that aren't needed anymore are DROPped.
>
> So far, so fine.
Do say, do you have any long-running transactions, or "idle"
transactions? Maybe someone opened a terminal somewhere and left it
open for days? Have a look at pg_stat_activity.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Juan Camilo Marín | 2009-05-13 17:58:51 | Re: lack in psql console |
Previous Message | Tom Lane | 2009-05-13 13:54:56 | Re: Failure during initdb - creating dictionaries ... FATAL: could not access file "$libdir/libdict_snowball": No such file or directory |