From: | Tatsuro Yamada <tatsuro(dot)yamada(dot)tf(at)nttcom(dot)co(dot)jp> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Duplicate history file? |
Date: | 2021-06-08 02:33:16 |
Message-ID: | dfd776a0-b8ba-fa7f-839d-9c9d143ab22b@nttcom.co.jp_1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021/06/07 17:32, Kyotaro Horiguchi wrote:
>>>> 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)
I should have told you that I would be happy to create a new thread.
Why I didn't create new thread is that because I didn't want people to
think I had hijacked the thread. :)
> 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
Thank you!
Regards,
Tatsuro Yamada
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Jacobson | 2021-06-08 02:48:20 | Re: security_definer_search_path GUC |
Previous Message | Japin Li | 2021-06-08 02:20:21 | Re: Confused about extension and shared_preload_libraries |