Re: API stability

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: boekewurm+postgres(at)gmail(dot)com
Cc: robertmhaas(at)gmail(dot)com, michael(at)paquier(dot)xyz, tgl(at)sss(dot)pgh(dot)pa(dot)us, markus(dot)wanner(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: API stability
Date: 2022-04-12 02:57:38
Message-ID: 20220412.115738.1512743305972578770.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

At Mon, 11 Apr 2022 12:48:25 +0200, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> wrote in
> On Mon, 11 Apr 2022 at 06:30, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> I won't speak for Robert H., but this might be because of gmail not
> putting this mail in the right thread: Your mail client dropped the
> "[was: pgsql: ...]" tag, which Gmail subsequently displays as a
> different thread (that is, in my Gmail UI there's three "Re: API
> stability" threads, one of which has the [was: pgsql: ...]-tag, and
> two of which seem to be started by you as a reply on the original
> thread, but with the [was: pgsql: ...]-tag dropped and thus considered
> a new thread).

Mmm. d*** gmail.. My main mailer does that defaltly but I think I can
*fix* that behavior.

Thanks!

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-04-12 03:49:48 Re: pgsql: Add TAP test for archive_cleanup_command and recovery_end_comman
Previous Message Tom Lane 2022-04-11 21:44:04 pgsql: Make XLogRecGetBlockTag() throw error if there's no such block.

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-04-12 03:49:48 Re: pgsql: Add TAP test for archive_cleanup_command and recovery_end_comman
Previous Message Peter Smith 2022-04-12 01:35:53 Re: row filtering for logical replication