Re: Set enable_seqscan doesn't take effect?

Поиск
Список
Период
Сортировка
От David Rowley
Тема Re: Set enable_seqscan doesn't take effect?
Дата
Msg-id CAApHDvrKZhJe7rUP0qnHKAL5xYid8t1y_OSOi3c_QN3fOZSZdQ@mail.gmail.com
обсуждение исходный текст
Ответ на Set enable_seqscan doesn't take effect?  (jacktby jacktby <jacktby@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Add test module for Table Access Method
Следующее
От: Peter Smith
Дата:
Сообщение: Re: [PGdocs] fix description for handling pf non-ASCII characters