Re: pgsql: Fix bug in Tid scan.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Fujii Masao <fujii(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix bug in Tid scan.
Date: 2020-02-08 03:05:00
Message-ID: 32239.1581131100@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> On Sat, Feb 8, 2020 at 11:08 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2020-02-08 03:30:23 pgsql: Revert recent change of ScanOption values and renumber SO_TYPE_T
Previous Message Fujii Masao 2020-02-08 02:48:22 Re: pgsql: Fix bug in Tid scan.