Search Postgresql Archives
Re: Declarative Range Partitioning Postgres 11
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: Declarative Range Partitioning Postgres 11
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Mon, 7 Oct 2019 17:17:47 -0600
Cc
: pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to
: <
F2F23E564EB92A4C80228EB86713BA130BD969@TO1RODC.nbspaymentsolutions.com
>
References
: <
F2F23E564EB92A4C80228EB86713BA130BD969@TO1RODC.nbspaymentsolutions.com
>
No, what you want is not possible and probably won't ever be I would expect. Scanning every partition to validate the primary key isn't scalable.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Follow-Ups
:
RE: Declarative Range Partitioning Postgres 11
From:
Shatamjeev Dewan
RE: Declarative Range Partitioning Postgres 11
From:
Shatamjeev Dewan
Re: Declarative Range Partitioning Postgres 11
From:
Ron
References
:
Declarative Range Partitioning Postgres 11
From:
Shatamjeev Dewan
Prev by Date:
Re: JSONB maximal length ?
Next by Date:
Re: Declarative Range Partitioning Postgres 11
Previous by thread:
Declarative Range Partitioning Postgres 11
Next by thread:
Re: Declarative Range Partitioning Postgres 11
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
