From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Duplicate history file? |
Date: | 2021-06-07 08:32:31 |
Message-ID: | 20210607.173231.257042332349870731.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(Sorry for the noise on the old thread..)
At Mon, 07 Jun 2021 16:54:49 +0900, Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> wrote in
> On 2021/06/07 16:31, Kyotaro Horiguchi wrote:
> > At Mon, 07 Jun 2021 16:13:08 +0900, Tatsuro Yamada
> > <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> wrote in
> >> I just noticed that this thread is still tied to another thread
> >> (it's not an independent thread). To fix that, it may be better to
> >> create a new thread again.
> > Mmm. Maybe my mailer automatically inserted In-Reply-To field for the
> > cited messsage. Do we (the two of us) bother re-launching a new
> > thread?
>
>
> The reason I suggested it was because I thought it might be
> confusing if the threads were not independent when registered in
> a commitfest. If that is not a problem, then I'm fine with it as
> is. :-D
(You can freely do that, too:p)
Hmm. I found that the pgsql-hackers archive treats the new thread as a
part of the old thread, so CF-app would do the same.
Anyway I re-launched a new standalone thread.
https://www.postgresql.org/message-id/20210607.173108.348241508233844279.horikyota.ntt%40gmail.com
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-06-07 08:52:10 | Re: SQL-standard function body |
Previous Message | Kyotaro Horiguchi | 2021-06-07 08:31:08 | Duplicate history file? |