Re: R: Vacuum full: alternatives? - Mailing list pgsql-general

From Martín Marqués
Subject Re: R: Vacuum full: alternatives?
Date
Msg-id CAPdiE1xHSa6FX2vdTfV=u4ABSE4uRcv9153pGcqf4_N05YiVWw@mail.gmail.com
Whole thread Raw
In response to Re: R: Vacuum full: alternatives?  (Vik Fearing <vik@2ndquadrant.fr>)
List pgsql-general
2016-06-20 11:30 GMT-03:00 Vik Fearing <vik@2ndquadrant.fr>:
> On 20/06/16 16:23, Martín Marqués wrote:
>>
>> That's not entirely true. Think about a SELECT which has to scan all
>> child tables.
>
> Or any SELECT on the parent at all.  The planner needs to examine the
> CHECK constraints on the children and can't do it if the child is locked
> in ACCESS EXCLUSIVE mode.

Yeah, totally skipped my mind that, so partitioning is actually a bad
idea, if that's all they are looking to solve.

Thanks Vik for showing the oversight

--
Martín Marqués                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Alex Ignatov
Date:
Subject: Re: R: Vacuum full: alternatives?
Next
From: Jeff Janes
Date:
Subject: Re: R: Vacuum full: alternatives?