>but the start time doesnt indicates that the object is the most recent, it
>just indicates when the object was added to your table…
>on each partition I'll create range partition on the end_date so that I can
>search for revisions faster.
I believe you are confusing data storage with que
but the start time doesnt indicates that the object is the most recent, it
just indicates when the object was added to your table. If your queries
involve the start_time I can understand why u set it as a partition column,
otherwise is isnt useful. In most of my queries I query by one of 2 options
From: Mariel Cherkassky
Sent: Wednesday, October 02, 2019 12:37 AM
Whenever I have a new revision of that object, I update the end_time of the
latest revision to be now() and I add a new record of that object with end_date
null.
The null value is used to find most recent revisions of objects..
Whenever I have a new revision of that object, I update the end_time of the
latest revision to be now() and I add a new record of that object with
end_date null.
The null value is used to find most recent revisions of objects..
Thanks for the suggestion of infinity ! I'll try it.
Mariel Cherkassky wrote:
> In PG12 I'm trying to create partitions by range on a date column
> that might be null (indicates it is the most recent version of the
> object). My PK has to include the partition column, therefore I'm
> getting an error that I cant create a primary key with the specific
