| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovacuum with inheritance |
| Date: | 2014-12-05 22:01:58 |
| Message-ID: | 1417816918729-5829461.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
yhe wrote
> From looking at the log, [...]
Any reason not to share it with the people from whom you are asking for
help?
> I was thinking that autovacuum should only happen on updated table so it
> should only autovacuum on one child and not the others for my case.
At the point of "stop usage" on the partition it would still want at least
one more cleanup vacuum; and eventually would want a FREEZE pass as well.
Furthermore, the parent of the partition scheme still needs to be aware of
the children and so you might be seeing that.
David J.
--
View this message in context: http://postgresql.nabble.com/autovacuum-with-inheritance-tp5829450p5829461.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Harding | 2014-12-06 00:55:10 | Array Comparison |
| Previous Message | Tom Lane | 2014-12-05 16:23:56 | Re: Multiple call handlers per language |