| From: | Sébastien <bokanist(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations |
| Date: | 2025-02-18 17:13:06 |
| Message-ID: | CANtq+vQUN=HVTFxYE4jeG2FKTxTvKcMjmyCtZ_0Vrdbh38ZqbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ok you mean that xid64 will remove the need for freezing... it's a way to
see things.
Le mar. 18 févr. 2025 à 15:57, Greg Sabino Mullane <htamfids(at)gmail(dot)com> a
écrit :
> On Tue, Feb 18, 2025 at 9:17 AM Sébastien <bokanist(at)gmail(dot)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
>
> --
> Crunchy Data - https://www.crunchydata.com
> Enterprise Postgres Software Products & Tech Support
>
>
--
Sébastien Caunes
+33 6 7 229 229 7
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthonin Bonnefoy | 2025-02-18 17:34:20 | Re: Add Pipelining support in psql |
| Previous Message | Sagar Shedge | 2025-02-18 17:06:00 | Re: Extend postgres_fdw_get_connections to return remote backend pid |