e
> should NOT exceed the physical memory of the database server."
That rule of thumb is correct (or at least not wrong). The reasoning behind it
is that table partitioning provides a benefit if individual partitions fit into
physical memory and queries target just a few partitions ins
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/ddl-partitioning.html
Description:
Is this rule of thumb a typo?
"The exact point at which a table will benefit from partitioning depends on
the application, although a rule of thumb is t
Bruce Momjian writes:
> On Thu, Jul 30, 2020 at 01:33:29PM +, PG Doc comments form wrote:
>> If I've well understood, this was not the case in previous versions, but it
>> becomes mandatory in version 12 (and maybe 11 too). Such restriction is not
>> mentioned in the documentation for version
On Thu, Jul 30, 2020 at 01:33:29PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/ddl-partitioning.html
> Description:
>
> With version 12 using declarative partitioning request that the column
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/ddl-partitioning.html
Description:
With version 12 using declarative partitioning request that the column used
for patitioning is part of the PRIMARY KEY of the table as you can see in
the
But how to create and manage these above 2 partition is not explained in
> > documentation properly officially.for further information related to
> these 2
> > partition we need to search private blogs,because of lack of information
> > provided in the document
pecified
> > remainder.
> >
> > But how to create and manage these above 2 partition is not explained in
> > documentation properly officially.for further information related to
> these 2
> > partition we need to search private blogs,because of lack of information
> &g
ge these above 2 partition is not explained in
> documentation properly officially.for further information related to these 2
> partition we need to search private blogs,because of lack of information
> provided in the documentation 5.10. Table Partitioning I only saw the Range
> partitio
ck of information
provided in the documentation 5.10. Table Partitioning I only saw the Range
partition example throughout the Table Partitioning .
I request you to modify the 5.10. Table Partitioning section and make it
more informative as Table Partition is very important in PostgreSQL .
Kind Re
On Tue, Jul 09, 2019 at 06:59:59PM -0400, Tom Lane wrote:
> Alvaro Herrera writes:
>>
>>
>>Unique constraints on partitioned tables (as well as primary keys)
>>must constrain all the partition key columns. This limitation exists
>>because PostgreSQL can only e
On Wed, Jul 10, 2019 at 7:53 AM Alvaro Herrera wrote:
> On 2019-Jul-09, Amit Langote wrote:
> > "While defining a primary key and unique constraints on partitioned
> > tables is supported, the set of columns being constrained must include
> > all of the partition key columns. This limitation exis
Alvaro Herrera writes:
> That's a mild personal preference only though. Anyway, based on your
> proposed wording, I wrote this:
>
>
>Unique constraints on partitioned tables (as well as primary keys)
>must constrain all the partition key columns. This limitation exi
On 2019-Jul-09, Amit Langote wrote:
> As mentioned in the docs, defining exclusion constraints on
> partitioned tables is not supported.
Right.
> "While defining a primary key and unique constraints on partitioned
> tables is supported, the set of columns being constrained must include
> all of
Sorry for jumping in late here.
On Tue, Jul 9, 2019 at 3:51 PM Michael Paquier wrote:
> On Tue, Jul 09, 2019 at 03:34:48PM +0900, Michael Paquier wrote:
> > Looking closely at the code in DefineIndex() (and as Rajkumar has
> > mentioned upthread for unique constraints) this can happen for primary
On Mon, Jul 8, 2019 at 11:34 PM Michael Paquier wrote:
> On Mon, Jul 08, 2019 at 08:12:18PM -0700, David G. Johnston wrote:
> > Reads a bit backward. How about:
> >
> > "As uniqueness can only be enforced within an individual partition when
> > defining a primary key on a partitioned table all c
On Tue, Jul 09, 2019 at 03:34:48PM +0900, Michael Paquier wrote:
> Looking closely at the code in DefineIndex() (and as Rajkumar has
> mentioned upthread for unique constraints) this can happen for primary
> keys, unique constraints and exclusion constraints. So we had better
> mention all three o
On Mon, Jul 08, 2019 at 11:10:51PM -0400, Tom Lane wrote:
> Isn't it the other way around, that the partition key column(s) must
> be
> included in the primary key? Maybe I'm confused, but it seems like
> we couldn't enforce PK uniqueness otherwise.
Yes you are right. The full column list of the
On Mon, Jul 08, 2019 at 08:12:18PM -0700, David G. Johnston wrote:
> Reads a bit backward. How about:
>
> "As uniqueness can only be enforced within an individual partition when
> defining a primary key on a partitioned table all columns present in the
> partition key must also exist in the prima
On Tue, Jul 9, 2019 at 8:29 AM Michael Paquier wrote:
> On Mon, Jul 08, 2019 at 10:37:37PM -0400, Bruce Momjian wrote:
> > On Fri, Jul 5, 2019 at 09:20:07PM +, PG Doc comments form wrote:
> >> In the documentation for Postgres 11 table partitioning, there is no
>
On Mon, Jul 8, 2019 at 7:59 PM Michael Paquier wrote:
> Attached is an idea of patch for the documentation, using this
> wording:
> +
> +
> + When defining a primary key on a partitioned table, the primary
> + key column must be included in the partition key.
> +
> +
Michael Paquier writes:
> Attached is an idea of patch for the documentation, using this
> wording:
> +
> +
> + When defining a primary key on a partitioned table, the primary
> + key column must be included in the partition key.
> +
> +
Isn't it the other way ar
On Mon, Jul 08, 2019 at 10:37:37PM -0400, Bruce Momjian wrote:
> On Fri, Jul 5, 2019 at 09:20:07PM +, PG Doc comments form wrote:
>> In the documentation for Postgres 11 table partitioning, there is no mention
>> of the requirement that the Primary Key of a partitioned tab
On Fri, Jul 5, 2019 at 09:20:07PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/ddl-partitioning.html
> Description:
>
> In the documentation for Postgres 11 table partiti
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/ddl-partitioning.html
Description:
In the documentation for Postgres 11 table partitioning, there is no mention
of the requirement that the Primary Key of a partitioned table must contain
24 matches
Mail list logo
