[bug] Wrong bool value parameter

From: 曾文旌 <wjzeng2012(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>
Subject: [bug] Wrong bool value parameter
Date: 2020-04-07 09:30:03
Message-ID: C6E8C2E7-1906-4F6E-BCC8-7D9FC2FC5CFE@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Do we allow such a bool parameter value? This seems puzzling to me.

postgres=# create table t1(c1 int) with(autovacuum_enabled ='tr');
CREATE TABLE
postgres=# create table t2(c1 int) with(autovacuum_enabled ='fa');
CREATE TABLE
postgres=# \d+ t1
Table "public.t1"
Column | Type | Collation | Nullable | Default | Storage | Stats target | Description
--------+---------+-----------+----------+---------+---------+--------------+-------------
c1 | integer | | | | plain | |
Access method: heap
Options: autovacuum_enabled=tr

postgres=# \d+ t2
Table "public.t2"
Column | Type | Collation | Nullable | Default | Storage | Stats target | Description
--------+---------+-----------+----------+---------+---------+--------------+-------------
c1 | integer | | | | plain | |
Access method: heap
Options: autovacuum_enabled=fa

I am try to fix in bug_boolrelopt.patch

Wenjing

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Grigory Smolkin 2020-04-07 09:36:18 Re: Don't try fetching future segment of a TLI.
Previous Message Michael Paquier 2020-04-07 08:17:32 Re: Don't try fetching future segment of a TLI.

Browse pgsql-hackers by date

  From Date Subject
Next Message Grigory Smolkin 2020-04-07 09:36:18 Re: Don't try fetching future segment of a TLI.
Previous Message Masahiko Sawada 2020-04-07 09:29:58 Re: pg_stat_statements issue with parallel maintenance (Was Re: WAL usage calculation patch)