From: | Bruno Hass <bruno_hass(at)LIVE(dot)COM> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | [Proposal] TOAST'ing in slices |
Date: | 2019-03-04 21:59:37 |
Message-ID: | BL0PR07MB40659940B4D360B4863C74CC91710@BL0PR07MB4065.namprd07.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Hackers,
I'm intending to optimize some varlena data types as my GSoC proposal. That would be done by a smarter way of splitting the TOAST table chunks, depending on its data type. A JSONB would be split considering its internal tree structure, keeping track of which keys are in each chunk. Arrays and text fields are candidates for optimization as well, as I outlined in my proposal draft (attached). Not being very familiar with the source code, I am writing to this list seeking some guidance in where to look in the source code in order to detail my implementation. Furthermore, I have a couple of questions:
* Would it be a good idea to modify the TOAST table row to keep metadata on the data it stores?
* This proposal will modify how JSONB, array and text fields are TOASTed. Where can I find the code related to that?
Kind regards,
Bruno Hass
Attachment | Content-Type | Size |
---|---|---|
PostgreSQL Proposal.pdf | application/pdf | 30.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2019-03-04 22:00:47 | Re: reloption to prevent VACUUM from truncating empty pages at the end of relation |
Previous Message | Thomas Munro | 2019-03-04 21:59:35 | Re: Rare SSL failures on eelpout |