| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: Avoid creation of the free space map for small tables |
| Date: | 2019-02-21 07:26:25 |
| Message-ID: | CACPNZCt4LGejsMNmUvzQdCPLWi5ARpaJaFsCs_BM1nE9Yf+7Yg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 21, 2019 at 7:58 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> So here you are inserting 4-byte integer and 1024-bytes variable
> length record. So the tuple length will be tuple_header (24-bytes) +
> 4-bytes for integer + 4-bytes header for variable length data + 1024
> bytes of actual data. So, the length will be 1056 which is already
> MAXALIGN. I took the new comments added in your latest version of the
> patch and added them to the previous version of the patch. Kindly
> see if I have not missed anything while merging the patch-versions?
OK, that makes sense. Looks fine to me.
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-02-21 07:40:13 | Re: Cache lookup errors with functions manipulation object addresses |
| Previous Message | Tsunakawa, Takayuki | 2019-02-21 07:09:33 | RE: Timeout parameters |