Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-committers-owner+archive@lists.postgresql.org>)
	id 1j0GQj-0005qA-2D
	for pgsql-committers@arkaria.postgresql.org; Sat, 08 Feb 2020 03:05:13 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-committers-owner+archive@lists.postgresql.org>)
	id 1j0GQg-00045S-Q0
	for pgsql-committers@arkaria.postgresql.org; Sat, 08 Feb 2020 03:05:10 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1j0GQg-00041t-Ez
	for pgsql-committers@lists.postgresql.org; Sat, 08 Feb 2020 03:05:10 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1j0GQZ-0007Lg-GL; Sat, 08 Feb 2020 03:05:08 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 018350Vn032240;
	Fri, 7 Feb 2020 22:05:00 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
cc: Fujii Masao <fujii@postgresql.org>, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix bug in Tid scan.
In-reply-to: 
 <CAHGQGwEQii11puP2nsF-7++G_+urNW_5cE_q01JGoCcVaDZxvQ@mail.gmail.com>
References: <E1j03Ml-0002mD-Hj@gemulon.postgresql.org>
 <5261.1581103527@sss.pgh.pa.us>
 <CAHGQGwFZ+KWahHGwqiJ676XHjHOoU_MKrS1gxie9zgw8pze+MQ@mail.gmail.com>
 <24554.1581123870@sss.pgh.pa.us>
 <CAHGQGwHhfvrj682CfykVZ-2wiYSY6DppxbdObSncd_pGWwRakw@mail.gmail.com>
 <29908.1581127702@sss.pgh.pa.us>
 <CAHGQGwEQii11puP2nsF-7++G_+urNW_5cE_q01JGoCcVaDZxvQ@mail.gmail.com>
Comments: In-reply-to Fujii Masao <masao.fujii@gmail.com>
	message dated "Sat, 08 Feb 2020 11:48:22 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <32238.1581131100.1@sss.pgh.pa.us>
Date: Fri, 07 Feb 2020 22:05:00 -0500
Message-ID: <32239.1581131100@sss.pgh.pa.us>
List-Id: <pgsql-committers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-committers@lists.postgresql.org>
List-Owner: <mailto:pgsql-committers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-committers>
Precedence: bulk

Fujii Masao <masao.fujii@gmail.com> writes:
> On Sat, Feb 8, 2020 at 11:08 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Personally I'd keep SO_TYPE_TIDSCAN physically adjacent to the other
>> SO_TYPE_xxxSCAN entries in the list, but of course that's just cosmetic.

> +1. So I will apply the latest patch (adding SO_TYPE_TIDSCAN just after
> SO_TYPE_ANALYZE) only to v12.

Works for me.

			regards, tom lane