| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Save a few bytes in pg_attribute |
| Date: | 2023-03-21 17:15:40 |
| Message-ID: | e9956cec-a91b-f374-e64d-c3c9c47eb32c@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21.03.23 17:43, Andres Freund wrote:
>> The context of my message was to do the proposed change for PG16 to buy back
>> a few bytes that are being added by another feature
> How much would you need to buy back to "reach parity"?
I don't think we can find enough to make the impact zero bytes. It's
also not clear exactly what the impact of each byte would be (compared
to possible complications in other parts of the code, for example). But
if there are a few low-hanging fruit, it seems like we could pick them,
to old us over until we have a better solution to the underlying issue.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberto Mello | 2023-03-21 17:17:41 | Re: PostgreSQL 16 Release Management Team & Feature Freeze |
| Previous Message | Robert Haas | 2023-03-21 17:12:39 | Re: CREATE DATABASE ... STRATEGY WAL_LOG issues |