MIME-Version: 1.0
References: <b11fa573-38fa-ba57-96a9-e4dd9ce3fb76@2ndquadrant.com>
 <CALAY4q-JMDqW5=LH6f70WhiO1+tP2NhGbWv_fjPtOt=KezchUQ@mail.gmail.com>
 <CAD21AoAUDJj_y_5fH5FLBLUDTZa579jbE5Y12SQz4nJh-RVx7A@mail.gmail.com>
 <CANbhV-EZu-SHXERZ=Bbq5g+ePi7QUX_0WgLtRsove_Jiigtaaw@mail.gmail.com>
 <CANbhV-EOTSc2EWS_LKiXKgLqnrjtaU0hf3Rzxn111nir6Pn4zA@mail.gmail.com>
 <CANbhV-ECkPhsXEtj7gYFjXCdq+3WTiHo9XkF5wQmFOj4w+YTaw@mail.gmail.com>
 <CANbhV-Fb35HMoySGMFfcxN_3i45Bb6cZODOcz8S7+Nys3Y2raA@mail.gmail.com>
 <CAN-V+g-D7bObC3m5rcm3zr8MmTVE4_OVJuEp8Qse0ZgE4PAhsw@mail.gmail.com>
 <CANbhV-F3S=5+5w19cowPwewBXSV3+C5T3BD327KQD7BLFgZbCQ@mail.gmail.com>
 <CAN-V+g_7EC=kAVeQV=+XL+KoV=QLdx_79J55OBarEYd49_uHRA@mail.gmail.com>
 <CANbhV-H-Wt7TVEwzzaYNEZ8-OteipdtvsxN1Qr1G9XpZoX2GgA@mail.gmail.com>
 <CANbhV-EymXWOFdX-Sz7PqQ8kphqHMteErBgD=FxmE+uF7jVW4w@mail.gmail.com>
 <7990518c-3dd3-4f30-c5e1-e094f6126e9a@postgresfriends.org>
 <CANbhV-Gee8avP652XoNikJrS2chxb9uo4zHujk4MMO1HW221vw@mail.gmail.com>
 <3a53c363-3e3f-813f-ad2f-c2f25ba8f006@postgresfriends.org>
In-Reply-To: <3a53c363-3e3f-813f-ad2f-c2f25ba8f006@postgresfriends.org>
From: Simon Riggs <simon.riggs@enterprisedb.com>
Date: Tue, 26 Jan 2021 13:26:06 +0000
Message-ID: 
 <CANbhV-HGL6V3EiCZzR1GtCQxfOZiO7CC6hbSn+_ZqBCYDBkikw@mail.gmail.com>
Subject: Re: WIP: System Versioned Temporal Table
To: Vik Fearing <vik@postgresfriends.org>
Cc: Ryan Lambert <ryan@rustprooflabs.com>,
 Masahiko Sawada <sawada.mshk@gmail.com>,
	Surafel Temesgen <surafel3000@gmail.com>,
 Michael Paquier <michael@paquier.xyz>,
	=?UTF-8?Q?R=C3=A9mi_Lapeyre?= <remi.lapeyre@lenstra.fr>,
	Eli Marmor <eli@netmask.it>, David Steele <david@pgmasters.net>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 Georgios <gkokolatos@protonmail.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Jan 26, 2021 at 12:51 PM Vik Fearing <vik@postgresfriends.org> wrote:
>
> On 1/26/21 1:16 PM, Simon Riggs wrote:
> > On Tue, Jan 26, 2021 at 11:33 AM Vik Fearing <vik@postgresfriends.org> wrote:
> >>
> >> On 1/11/21 3:02 PM, Simon Riggs wrote:
> >>> * UPDATE foo SET start_timestamp = DEFAULT should fail but currently doesn't
> >>
> >> I'm still in the weeds of reviewing this patch, but why should this
> >> fail?  It should not fail.
> >
> > It should not be possible for the user to change the start or end
> > timestamp of a system_time time range, by definition.
>
> Correct, but setting it to DEFAULT is not changing it.
>
> See also SQL:2016 11.5 <default clause> General Rule 3.a.

Thanks for pointing this out. Identity columns don't currently work that way.

-- 
Simon Riggs                http://www.EnterpriseDB.com/