Re: [HACKERS] [COMMITTERS] pgsql: Implement table partitioning. - Mailing list pgsql-hackers

From Christophe Pettus
Subject Re: [HACKERS] [COMMITTERS] pgsql: Implement table partitioning.
Date
Msg-id F0C67105-ADFE-4A47-B461-DC5230D6BE43@thebuild.com
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Implement table partitioning.  (Keith Fiske <keith@omniti.com>)
Responses Re: [HACKERS] [COMMITTERS] pgsql: Implement table partitioning.  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
> On Dec 9, 2016, at 22:52, Keith Fiske <keith@omniti.com> wrote:
> On Fri, Dec 9, 2016 at 10:01 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> One thing that's tricky/annoying about this is that if you have a
>> DEFAULT partition and then add a partition, you have to scan the
>> DEFAULT partition for data that should be moved to the new partition.
>> That makes what would otherwise be a quick operation slow.  Still, I'm
>> sure there's a market for that feature.
>
> I would find that perfectly acceptable as long as a caveat about the performance impact was included in the
documentation.

+1.  I don't think it's conceptually different from adding a column with a default, in that regard; you just have to
knowthe impact. 


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Effect of caching hash bucket size while costing
Next
From: Artur Zakirov
Date:
Subject: Re: [HACKERS] [sqlsmith] Crash in tsquery_rewrite/QTNBinary