Re: Disable vacuuming to provide data history
От | Vik Fearing |
---|---|
Тема | Re: Disable vacuuming to provide data history |
Дата | |
Msg-id | ad2cd43b-0e98-1683-99c8-e9d54bacdb26@postgresfriends.org обсуждение исходный текст |
Ответ на | Re: Disable vacuuming to provide data history (Corey Huinker <corey.huinker@gmail.com>) |
Ответы |
Re: Disable vacuuming to provide data history
Re: Disable vacuuming to provide data history |
Список | pgsql-hackers |
On 2/24/23 22:06, Corey Huinker wrote: > On Thu, Feb 23, 2023 at 6:04 AM <marekmosiewicz@gmail.com> wrote: > > [1] some implementations don't use null, they use an end-timestamp set to > a date implausibly far in the future ( 3999-12-31 for example ), The specification is, "At any point in time, all rows that have their system-time period end column set to the highest value supported by the data type of that column are known as current system rows; all other rows are known as historical system rows." I would like to see us use 'infinity' for this. The main design blocker for me is how to handle dump/restore. The standard does not bother thinking about that. -- Vik Fearing
В списке pgsql-hackers по дате отправления: