Re: pgsql: Introduce hash_search_with_hash_value() function - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgsql: Introduce hash_search_with_hash_value() function
Date
Msg-id CA+Tgmoa+PkfF0YqFe46V1n3vszD-EuFbf5GeS285cMW85cE=6g@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Introduce hash_search_with_hash_value() function  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: pgsql: Introduce hash_search_with_hash_value() function
List pgsql-hackers
On Wed, Aug 7, 2024 at 1:15 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> > We could use git notes.  The UI is a bit inconvenient (they have to be
> > pushed and pulled separately from commits), but they seem useful enough.
>
> Yeah, I spend a lot of time on commit messages because they're pretty much
> written in stone once pushed.  I'd definitely use git notes to add errata,
> follow-up commits that fixed/reverted things, etc.

I think this could be a good idea, although it wouldn't really fix the
problem, because in the case of both this commit and the one I
mentioned earlier today, all you could do with the note is point out
the earlier mistake. You couldn't actually fix it.

Also, for the notes to be useful, we'd probably need some conventions
about how we, as a project, want to use them. If everyone does
something different, the result isn't likely to be all that great.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_verifybackup: TAR format backup verification
Next
From: David Zhang
Date:
Subject: Re: Proposal for implementing OCSP Stapling in PostgreSQL