From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "Alex V(dot)" <in_flight(at)pclovers(dot)ru>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, tgl <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Table partition with primary key in 11.3 |
Date: | 2019-06-07 23:58:29 |
Message-ID: | CAH2-Wzn4guNHAyRCwNOkGCbRO8=H8G_JQRXZirZ074EY=oRozA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 7, 2019 at 2:35 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> I envision this happening automatically -- you drop the partition, a
> persistent work item is registered, autovacuum takes care of it
> whenever. The user doesn't have to do anything about it.
We don't have to agree on anything now, but I think that it's possible
that the page split thing will very effective. Perhaps even so
effective that it won't make much sense to vacuum global indexes just
because there is a pending dropped partition.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2019-06-08 10:31:06 | Re: Postgres 10.7 Systemd Startup Issue |
Previous Message | Alvaro Herrera | 2019-06-07 21:35:32 | Re: Table partition with primary key in 11.3 |