Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations
Date
Msg-id CAKAnmmKzmTQTKXQ62U0s3tw-bBL3wUqY5UWqNd4B2eiVyvTh5g@mail.gmail.com
Whole thread Raw
In response to Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations  (Sébastien <bokanist@gmail.com>)
Responses Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations
List pgsql-hackers
On Tue, Feb 18, 2025 at 9:17 AM Sébastien <bokanist@gmail.com> wrote:
Sorry it won't work. It just delays the problem. But still the freeze procedure must rewrite all pages.

Actually, a 64-bit transaction ID allows for quite a "delay" - like hundreds of millions of years at your current rate. :) 

(Yes, there are other reasons to vacuum, and other limits and problems would arise. You'd have 99 problems, but a vacuum freeze ain't one.)

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Bug in nbtree SAOP scans with non-required arrays, truncated high key
Next
From: Andrew Dunstan
Date:
Subject: Re: New "single" COPY format