Re: WIP: System Versioned Temporal Table - Mailing list pgsql-hackers

From Ryan Lambert
Subject Re: WIP: System Versioned Temporal Table
Date
Msg-id CAN-V+g98BC0K+z8LdQOKWwW+0Lv6CeqGdvPtHneWscheRwYQ6Q@mail.gmail.com
Whole thread Raw
In response to Re: WIP: System Versioned Temporal Table  (Simon Riggs <simon.riggs@enterprisedb.com>)
List pgsql-hackers

On Thu, Jan 14, 2021 at 2:22 PM Simon Riggs <simon.riggs@enterprisedb.com> wrote:
On Thu, Jan 14, 2021 at 5:46 PM Surafel Temesgen <surafel3000@gmail.com> wrote:

> On Fri, Jan 8, 2021 at 7:50 PM Ryan Lambert <ryan@rustprooflabs.com> wrote:
>>
>> I prefer to have them hidden by default.  This was mentioned up-thread with no decision, it seems the standard is ambiguous.  MS SQL appears to have flip-flopped on this decision [1].

I think the default should be like this:

SELECT * FROM foo FOR SYSTEM_TIME AS OF ...
should NOT include the Start and End timestamp columns
because this acts like a normal query just with a different snapshot timestamp

SELECT * FROM foo FOR SYSTEM_TIME BETWEEN x AND y
SHOULD include the Start and End timestamp columns
since this form of query can include multiple row versions for the
same row, so it makes sense to see the validity times

+1

Ryan Lambert 

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2
Next
From: David Zhang
Date:
Subject: Re: Add table access method as an option to pgbench