From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
Cc: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, 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> |
Subject: | Re: WIP: System Versioned Temporal Table |
Date: | 2021-01-18 18:56:13 |
Message-ID: | CALAY4q_dyKtJC1pSAU7srncTWUiQKtLT+2n7pruS-X46yy2ZWw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 18, 2021 at 1:43 AM Vik Fearing <vik(at)postgresfriends(dot)org> wrote:
>
> This is not good, and I see that DROP SYSTEM VERSIONING also removes
> these columns which is even worse. Please read the standard that you
> are trying to implement!
>
>
The standard states the function of ALTER TABLE ADD SYSTEM VERSIONING
as "Alter a regular persistent base table to a system-versioned table" and
system versioned table is described in the standard by two generated
stored constraint columns and implemented as such.
> I will do a more thorough review of the functionalities in this patch
> (not necessarily the code) this week.
>
>
Please do
regards
Surafel
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-01-18 18:58:20 | Re: Key management with tests |
Previous Message | Tom Lane | 2021-01-18 18:46:48 | Re: search_plan_tree(): handling of non-leaf CustomScanState nodes causes segfault |