From: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
---|---|
To: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: SQL:2011 application time |
Date: | 2022-01-06 18:52:30 |
Message-ID: | CADkLM=cDpJ=Q_wVgsG3MxB4PRKcprnoJ_zJuAWCpxA-pyj88dQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
>
> But
> the standard says that dropping system versioning should automatically
> drop all historical records (2 under Part 2: Foundation, 11.30 <drop
> system versioning clause>). That actually makes sense though: when you
> do DML we automatically update the start/end columns, but we don't
> save copies of the previous data (and incidentally the end column will
> always be the max value.)
This is what I was referring to when I mentioned a side-table.
deleting history would be an O(1) operation. Any other
misunderstandings are all mine.
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Jacobson | 2022-01-06 19:02:03 | Re: pl/pgsql feature request: shorthand for argument and local variable references |
Previous Message | Pavel Stehule | 2022-01-06 18:32:54 | Re: pl/pgsql feature request: shorthand for argument and local variable references |