Re: WIP: System Versioned Temporal Table

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Surafel Temesgen <surafel3000(at)gmail(dot)com>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Cc: Ryan Lambert <ryan(at)rustprooflabs(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Rémi Lapeyre <remi(dot)lapeyre(at)lenstra(dot)fr>, Eli Marmor <eli(at)netmask(dot)it>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Georgios <gkokolatos(at)protonmail(dot)com>, Vik Fearing <vik(dot)fearing(at)enterprisedb(dot)com>
Subject: Re: WIP: System Versioned Temporal Table
Date: 2021-01-16 14:08:48
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 1/14/21 6:42 PM, Surafel Temesgen wrote:
> Hi Simon,
> Thank you for all the work you does
> On Mon, Jan 11, 2021 at 5:02 PM Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
> wrote:
>> * Anomalies around use of CURRENT_TIMESTAMP are not discussed or resolved.
>> Probably need to add a test that end_timestamp > start_timestamp or ERROR,
>> which effectively enforces serializability.
> This scenario doesn't happen.

It *does* happen and the standard even provides a specific error code
for it (2201H).

Please look at my extension for this feature which implements all the
requirements of the standard (except syntax grammar, of course).
Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Anastasia Lubennikova 2021-01-16 15:11:29 Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Previous Message Vik Fearing 2021-01-16 14:03:49 Re: WIP: System Versioned Temporal Table