Re: API stability

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: API stability
Date: 2022-04-11 18:00:34
Message-ID: CA+TgmoahHVYDJhuEQ7WesTusTiiFaRyNaD4BRe6k+mvHV6fzpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Apr 11, 2022 at 6:48 AM Matthias van de Meent
<boekewurm+postgres(at)gmail(dot)com> wrote:
> So, this might be the reason Robert overlooked your declaration to
> volunteer: he was looking for volunteers in the thread "Re: API
> Stability [was: pgsql: ...]" in the Gmail UI, which didn't show your
> messages there because of the different subject line.

Yes, that's what happened.

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Thom Brown 2022-04-11 18:51:03 Re: [COMMITTERS] pgsql: Allow time delayed standbys and recovery
Previous Message Tom Lane 2022-04-11 17:22:40 pgsql: Explicitly ignore guaranteed-true result from pgstat_lock_entry(

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-04-11 18:20:21 Fixing code that ignores failure of XLogRecGetBlockTag
Previous Message Robert Haas 2022-04-11 17:59:08 Re: typos