Re: autovac hung/blocked - Mailing list pgsql-general

From Ed L.
Subject Re: autovac hung/blocked
Date
Msg-id 200611160908.34980.pgsql@bluepolka.net
Whole thread Raw
In response to Re: autovac hung/blocked  (Richard Huxton <dev@archonet.com>)
List pgsql-general
On Thursday November 16 2006 3:33 am, Richard Huxton wrote:
> Ed L. wrote:
> > One idea would be to partition the table some how such that
> > the chunks getting vacuumed are much smaller and thus not
> > such an impact.  On the app side, I suppose we could break
> > the table into multiple tables on some dimension (time) to
> > make the vacuum impacts smaller.
>
> You're running on bigger datasets than I'm used to, but that
> would be my approach. Did you notice the constraint
> partitioning introduced in 8.1?
>
> http://www.postgresql.org/docs/8.1/static/ddl-partitioning.htm
>l#DDL-PARTITIONING-CONSTRAINT-EXCLUSION

Thanks for the tip.  We have avoided use of inheritance in order
to stay closer to the beaten path, but the partitioning
implementation ideas are useful.

Ed

pgsql-general by date:

Previous
From: "Ardian Xharra"
Date:
Subject: Re: Why the data changes it's value by itself!
Next
From: brian
Date:
Subject: Re: Strange Postgresql crash