Re: Partitioning on the date part of a timestamp & PK issues

On 7/15/21 9:53 PM, Alvaro Herrera wrote:
> On 2021-Jul-15, Ron wrote:
>
>> 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, ts)
>> )   partition by range (ts);
> This definition will let you have multiple rows for the same
> (guid,tid,seq) combination, as long as they have different ts values.
> That is at odds with the original formulation, in which there could be a
> single row with any given combination of those three columns.

That's the cost of partitioning by something other than uid, tid or seq.

--
Angular momentum makes the world go 'round.