Re: pgsql: Use CompactAttribute more often, when possible

From: David Rowley <dgrowley(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Use CompactAttribute more often, when possible
Date: 2025-10-23 18:43:09
Message-ID: CAHoyFK_vC6wsrJ+ws-tziZ0fPUsPiYTuzsr+aY+YnJ3Q4KuhPg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, 24 Oct 2025 at 01:21, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> David, I've noticed several times lately you've documented in commit
> messages why you thought going further with some change would be
> risky, and I really like that. I think sometimes we (as committers)
> are sometimes reluctant to document cases where we weren't sure about
> something or didn't know something, but IMHO this sort of
> documentation of perceived risk is a huge help to anyone who is
> thinking of working in this area later. Whether or not they agree with
> your conclusions, they'll find it helpful to know your thought
> process.

Thanks. But part of that was from motivation to try and stop the
"hey, you forgot this one!" follow-up emails. :)

David

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-10-23 19:45:08 pgsql: doc: Remove mention of Git protocol support
Previous Message Tom Lane 2025-10-23 18:23:31 pgsql: Avoid memory leak in validation of a PL/Python trigger function.

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-10-23 18:47:51 Re: another autovacuum scheduling thread
Previous Message Sami Imseih 2025-10-23 18:22:24 Re: another autovacuum scheduling thread