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

From Vik Fearing
Subject Re: R: Vacuum full: alternatives?
Date
Msg-id 5767FE1A.3030100@2ndquadrant.fr
Whole thread Raw
In response to Re: R: Vacuum full: alternatives?  (Martín Marqués <martin@2ndquadrant.com>)
Responses Re: R: Vacuum full: alternatives?
Re: R: Vacuum full: alternatives?
List pgsql-general
On 20/06/16 16:23, Martín Marqués wrote:
> El 20/06/16 a las 09:50, Melvin Davidson escribió:
>>
>>
>>> but it won't let it grow too (or am I missing something).
>>
>> Yes, you are missing something. By partioning and {Vacuum Full only the
>> table with data no longer needed}, the rest of the data remains
>> available to the users
>> AND space is reclaimed by the O/S, so it's the best of both worlds.
>
> 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.
--
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-general by date:

Previous
From: Martín Marqués
Date:
Subject: Re: R: Vacuum full: alternatives?
Next
From: Alex Ignatov
Date:
Subject: Re: R: Vacuum full: alternatives?