| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Introduce hash_search_with_hash_value() function |
| Date: | 2024-08-23 14:49:17 |
| Message-ID: | CA+Tgmoa0gn+8++5NyLX1m_UYR3mU5u=hS7zHmOZn+32KL96VwQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Aug 15, 2024 at 5:02 PM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
> On Wed, Aug 07, 2024 at 02:01:30PM -0400, Robert Haas wrote:
> > 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.
>
> What did you have in mind? Would it be sufficient to propose a template
> that, once ratified, would be available in the committing checklist [0]?
>
> [0] https://wiki.postgresql.org/wiki/Committing_checklist
Yes, that would suffice.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-08-24 14:02:59 | pgsql: pg_createsubscriber: Message style improvements |
| Previous Message | Tom Lane | 2024-08-23 14:13:01 | pgsql: Provide feature-test macros for libpq features added in v17. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2024-08-23 15:16:57 | Re: On disable_cost |
| Previous Message | Jelte Fennema-Nio | 2024-08-23 14:42:27 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |