| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, Greg Burd <greg(at)burd(dot)me>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Support for 8-byte TOAST values, round two |
| Date: | 2026-09-30 10:44:28 |
| Message-ID: | CAMT0RQSEvkAEXPtnWzuzQZovYscjQUeiVsSv_QfLQirdWuQ3wg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In my insert tests 8-byte TOAST was much faster that 4-byte toast
During a 30 min run inserting tuples with 8 toasted fields of ~100
bytes oid8 toast kept a steady 18k inserts / second against 14.6k
inserts second for oid4
This resulted in a solid 23% speed-up because it didn't need to verify
new OIDs against the unique index, despite each toast index entry
taking up slightly more space (30.1 bytes vs. 21.4 bytes on average)
On Wed, Sep 23, 2026 at 12:58 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Sep 22, 2026 at 03:35:00PM -0700, Bharath Rupireddy wrote:
> > Agreed. Using OID/OID8 values and breaking up the sentences reads
> > better. Please find the attached v2 patch.
>
> Pushed.
> --
> Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2026-09-30 10:45:48 | Re: postgres_fdw: transaction mode inheritance corner cases |
| Previous Message | Nisha Moond | 2026-09-30 10:34:56 | Re: Fix apply worker crash when subscriber table has only a deferrable primary key |