Re: Speedup truncations of temporary relation forks
Daniil Davydov <3danissimo@gmail.com>
From: Daniil Davydov <3danissimo@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-02T06:23:41Z
Lists: pgsql-hackers
Hi, On Mon, Jun 2, 2025 at 11:14 AM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > > (I haven't figured out how to force postgres to > > create a visibility map for temp table within the transaction block). > > I haven't tested this, but I think if you do bulk copy into a table > which should mark pages all visible and after that if you delete some > tuple from pages logically it should try to update the status to not > all visible in vm? > I found reliable way to create all three forks : begin; create temp table test (id int) on commit delete rows; copy test from 'data.csv' with (freeze); insert into test select generate_series(2000000, 3000000); delete from test where id % 500000 = 0; commit; -- Best regards, Daniil Davydov
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Speed up truncation of temporary relations.
- 78ebda66bf26 19 (unreleased) landed
-
Speedup truncations of relation forks.
- 6d05086c0a79 13.0 cited