Search Postgresql Archives

RE: Declarative Range Partitioning Postgres 11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Michael,

 

In this case , I always need to include partition key(date)  in primary key ( if I have a primary key defined on non partition key column e.g id (in my case), to make it a composite primary key (id, date). This would allow duplicate id with different date,which is not desirable .

 

Thanks,

Shatamjeev

 

From: Michael Lewis <mlewis@xxxxxxxxxxx>
Sent: October-07-19 7:18 PM
To: Shatamjeev Dewan <sdewan@xxxxxxxxx>
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: Declarative Range Partitioning Postgres 11

 

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]
[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]

  Powered by Linux