From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Storage Model for Partitioning |
Date: | 2008-01-11 10:59:14 |
Message-ID: | 162867790801110259v7fc706f5l6966815df380f921@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> 3. Partitions are RelFileNodes, but not Tables
>
> We allow a table to have multiple RelFileNodes, when explicitly declared
> that way.
>
> This means we have to change
> - DDL changes to allow TABLE level changes to apply to all RelFileNodes,
> while PARTITION level changes to apply to only one RelFileNode
> - indexes, so they can refer to more than one partition
> - share locking in the executor
> - changes to allow synchronous scans and buffer recycling
>
> There *are* other changes not mentioned here that are required for
> partitioning, which although complex are less doubtful.
>
It can be used for global temporary tables with some modification
table defines structure and partitions defines contents for sessions.
Regards
Pavel Stehule
> Simon Riggs
> 2ndQuadrant http://www.2ndQuadrant.com
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2008-01-11 11:34:17 | Re: Storage Model for Partitioning |
Previous Message | Simon Riggs | 2008-01-11 10:25:40 | Storage Model for Partitioning |