We need insert rows to a catalog table that would store partitions info:
CATALOG(pg_partition,2336) BKI_WITHOUT_OIDS
{
Oid partrelid; /* partition table Oid */
Oid parentrelid;/* Parent table Oid */
int2parttype; /* Type of partition, list, hash,
Hi Robert,
> I am a little fuzzy on what you're proposing here, but I think you're
> saying that you're only going to support range partitioning on
> integers or dates and that you plan to use the text type to store the
> integer or date values. FWIW, those don't seem like very good
> decisio
Thanks for your feedback, Emmanuel.
Here are my comments:
On 2/10/09, Emmanuel Cecchet wrote:
> Hi Amit,
>
> I will be traveling until next Tuesday and will have no access to email so
> don't be surprised if I don't follow up this week.
> The overall approach seems sound. The metadata table sho
Hi Emmanuel,
We are considering to following approach:
1. metadata table pg_partitions is defined as follows:
CATALOG(pg_partitions,2336) BKI_WITHOUT_OIDS
{
Oid partrelid; // partition table Oid
Oid parentrelid; // Parent table Oid
int4parttype; // Type o
While trying to figure out an appropriate cost expression function for
Thick indexes, i learned that we are using Mackert and Lohman formula
(described in their paper "Index Scans Using a Finite LRU Buffer: A
Validated I/O Model", ACM Transactions on Database Systems).
The paper's result is as foll
Hi Emmanuel,
On 1/26/09, Emmanuel Cecchet wrote:
>
> Hi Amit,
>
> I overlooked the fact that you dropped composite partitions and
> subpartitions template from the proposal presented in
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php.
> Is it because this is too hard to suppo
Hi Emmanuel,
Please find my comments in-lined:
On 1/23/09, Emmanuel Cecchet wrote:
>
> Amit,
>
> You might want to put this on the
> http://wiki.postgresql.org/wiki/Table_partitioning wiki page.
Sure.
How does your timeline look like for this implementation?
The implementation is planned a
Hi,
We are implementing table partitioning feature to support
- the attached commands. The syntax conforms to most of the suggestion
mentioned in
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php, barring
the following:
-- Specification of partition names is optional. System will b
Hi,
We are extending Gokul's Thick index functionality (
http://archives.postgresql.org/pgsql-patches/2008-01/msg00092.php) on 8.4
code base to
- fix existing defects
- Extend thick index usage for group by, count, nested queries, and
"delete/update with join" queries.
- Improve cost estimates for
