Re: Optimize partial TOAST decompression
Tomas Vondra <tomas.vondra@2ndquadrant.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Binguo Bao <djydewang@gmail.com>, Andrey Borodin <x4mmm@yandex-team.ru>, Paul Ramsey <pramsey@cleverelephant.ca>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-26T23:00:36Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Properly determine length for on-disk TOAST values
- 2dc08bd6179d 13.0 landed
-
Blind attempt to fix pglz_maximum_compressed_size
- 540f31680913 13.0 landed
-
Optimize partial TOAST decompression
- 11a078cf87ff 13.0 landed
Attachments
- 0001-Optimize-partial-TOAST-decompression-7.patch (text/plain)
On Wed, Sep 25, 2019 at 05:38:34PM -0300, Alvaro Herrera wrote: >Hello, can you please update this patch? > I'm not the patch author, but I've been looking at the patch recently and I have a rebased version at hand - so attached. FWIW I believe the patch is solid and in good shape, and it got stuck after I reported some benchmarks showing somewhat flaky performance. I know Binguo Bao was trying to reproduce the benchmark, and I assume the silence means he was not successful :-( On the larger data set the patch however performed very nicely, so maybe I just did something stupid while running the smaller one, or maybe it's just noise (the queries were just a couple of ms in that test). I do plan to rerun the benchmarks and investigate a bit - if I find the patch is fine, I'd like to commit it shortly. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services