Re: VACUUM fails to parse 0 and 1 as boolean value

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM fails to parse 0 and 1 as boolean value
Date: 2019-05-22 16:20:53
Message-ID: CAHGQGwFf_aUqjDrkoXOyrTBwXo28-MaH6h_gOzpoipAsabi1ig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 22, 2019 at 4:47 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Wed, May 22, 2019 at 04:32:38AM +0900, Fujii Masao wrote:
> > I found that tab-completion also needs to be updated for ANALYZE
> > boolean options. I added that change for tab-completion into
> > the patch and am thinking to apply the attached patch.
>
> Looks fine to me at quick glance.

Thanks! Committed.

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-05-22 16:43:19 Re: Why does ExecComputeStoredGenerated() form a heap tuple
Previous Message Tom Lane 2019-05-22 15:52:46 Re: "long" type is not appropriate for counting tuples