Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: bokanist(at)gmail(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Feature Request] INSERT FROZEN to Optimize Large Cold Data Imports and Migrations
Date: 2025-02-13 16:14:01
Message-ID: CAKAnmmLwWxntKiDjnY=wPK93TomdSAuheXJix1d6sZVze_HNPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 13, 2025 at 9:45 AM Sébastien <bokanist(at)gmail(dot)com> wrote:

> This issue is particularly critical during database *migrations* or *version
> upgrades*, where a full data reload is often necessary. Each time a major
> PostgreSQL upgrade occurs, users must reimport large datasets, leading to
> the same problem of vacuum storms post import.
>

What major upgrade process are you doing that uses INSERT?

Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-02-13 16:28:53 Re: BitmapHeapScan streaming read user and prelim refactoring
Previous Message Yugo Nagata 2025-02-13 16:02:18 Remove a unnecessary argument from execute_extension_script()