From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | jacktby jacktby <jacktby(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Set enable_seqscan doesn't take effect? |
Date: | 2023-09-28 01:11:06 |
Message-ID: | CAApHDvrKZhJe7rUP0qnHKAL5xYid8t1y_OSOi3c_QN3fOZSZdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 28 Sept 2023 at 13:47, jacktby jacktby <jacktby(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2023-09-28 01:13:40 | Re: [PGdocs] fix description for handling pf non-ASCII characters |
Previous Message | Michael Paquier | 2023-09-28 01:08:24 | Re: Add test module for Table Access Method |