| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remaining sql/json patches |
| Date: | 2024-03-07 02:50:09 |
| Message-ID: | CACJufxFf3xQhMeUujViWK=77hCJ-NiESjTdYyZ10ysd7gckcSQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 6, 2024 at 9:22 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>
> Another case, I did test yet: more keys in a single json, but the
> value is small.
Another case attached. see the attached SQL file's comments.
a single simple jsonb, with 33 keys, each key's value with fixed length: 256.
total table size: SELECT pg_size_pretty(pg_table_size('json33keys')); --5369 MB
number of rows: 600001.
using the previously mentioned method: pg_log_backend_memory_contexts.
all these tests under:
-Dcassert=true \
-Db_coverage=true \
-Dbuildtype=debug \
I hope someone will tell me if the test method is correct or not.
| Attachment | Content-Type | Size |
|---|---|---|
| jsonb_33keys.sql | application/sql | 33.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-03-07 03:00:23 | Re: Confine vacuum skip logic to lazy_scan_skip |
| Previous Message | Tender Wang | 2024-03-07 02:24:00 | Re: "type with xxxx does not exist" when doing ExecMemoize() |