Re: Partitioning on the date part of a timestamp & PK issues - Mailing list pgsql-admin

From Ron
Subject Re: Partitioning on the date part of a timestamp & PK issues
Date
Msg-id 13f09d24-a255-ac33-7745-6a2f59d49679@gmail.com
Whole thread Raw
In response to Partitioning on the date part of a timestamp & PK issues  (Wells Oliver <wells.oliver@gmail.com>)
Responses Re: Partitioning on the date part of a timestamp & PK issues
List pgsql-admin
On 7/15/21 3:10 PM, Wells Oliver wrote:
> I have a table like so:
>
> CREATE TABLE t (
>     guid uuid not null,
>     seq smallint not null,
>     tid smallint not null,
>     ts timestamp without time zone not null,
>     x real,
>     y real,
>     z real,
>     primary key (guid, tid, seq)
> ) partition by range (extract(date from ts));
>
> Which results in the error:
>
> ERROR:  unsupported PRIMARY KEY constraint with partition key definition
> DETAIL:  PRIMARY KEY constraints cannot be used when partition keys 
> include expressions.
>
> Is there a suitable way to get around this? I can make an additional date 
> col in the table to use for the partition range, but given the amount of 
> data we will have, I am trying to be cognizant of storage concerns.
>
> The PK is the PK, so I'm not sure what options I have there.

Why do you feel the need to "extract(date from ts)" instead of just 
partitioning by "ts"?

-- 
Angular momentum makes the world go 'round.



pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Partitioning on the date part of a timestamp & PK issues
Next
From: Wells Oliver
Date:
Subject: Re: Partitioning on the date part of a timestamp & PK issues