| From: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com>, Scott Mead <scottm(at)openscg(dot)com> |
| Cc: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, Job <Job(at)colliniconsulting(dot)it>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: R: Vacuum full: alternatives? |
| Date: | 2016-06-20 15:18:58 |
| Message-ID: | 599301d6-7fbf-82f4-20c5-0c9368b872cc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
El 20/06/16 a las 12:06, Melvin Davidson escribió:
>
> Martin and Vik,
>
>>...Think about a SELECT which has to scan all child tables.
>
> You are really digging for a corner case.
> If a scan has to scan all child tables, then
> A. it negates the ability to make partitions which are not used
> and
> B. The SELECT query is poorly crafted.
And you haven't read Vik's reply. :)
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2016-06-20 15:25:49 | Re: R: Vacuum full: alternatives? |
| Previous Message | Guillaume Lelarge | 2016-06-20 15:10:45 | Re: R: Vacuum full: alternatives? |