Re: Set enable_seqscan doesn't take effect? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Set enable_seqscan doesn't take effect?
Date
Msg-id CAApHDvrKZhJe7rUP0qnHKAL5xYid8t1y_OSOi3c_QN3fOZSZdQ@mail.gmail.com
Whole thread Raw
In response to Set enable_seqscan doesn't take effect?  (jacktby jacktby <jacktby@gmail.com>)
List pgsql-hackers
On Thu, 28 Sept 2023 at 13:47, jacktby jacktby <jacktby@gmail.com> wrote:
>
> postgres=# SET enable_seqscan = off;
> SET
> postgres=# explain select * from t;
>                                QUERY PLAN
> -------------------------------------------------------------------------
>  Seq Scan on t  (cost=10000000000.00..10000000023.60 rows=1360 width=32)
> (1 row)
>
> postgres=#  select * from t;
>    a
> -------
>  [1,2]
> (1 row)>

It may be worth checking what the manual says about this. I guess if
you assume the meaning from the GUC name, then it might be surprising.
If you're still surprised after reading the manual then please report
back.

David



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add test module for Table Access Method
Next
From: Peter Smith
Date:
Subject: Re: [PGdocs] fix description for handling pf non-ASCII characters