Re: Set enable_seqscan doesn't take effect?

From: jacktby jacktby <jacktby(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: andres(at)anarazel(dot)de
Subject: Re: Set enable_seqscan doesn't take effect?
Date: 2023-09-28 03:45:34
Message-ID: C26E8662-90FB-4AB6-990E-1CC51EA496E4@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 2023年9月28日 01:07,Andres Freund <andres(at)anarazel(dot)de> 写道:
>
> Hi,
>
> On 2023-09-28 00:37:41 +0800, jacktby jacktby 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)
>
> Sorry to be the grump here:
>
> You start several threads a week, often clearly not having done much, if any,
> prior research. Often even sending the same question to multiple lists. It
> should not be hard to find an explanation for the behaviour you see here.
>
> pgsql-hackers isn't a "do my work for me service". We're hacking on
> postgres. It's fine to occasionally ask for direction, but you're very clearly
> exceeding that.
>
> Greetings,
>
> Andres Freund
I’m so sorry for that. I think I’m not very familiar with pg, so I ask many naive questions. And I apologize for my behavior.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-09-28 03:51:38 Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
Previous Message jacktby jacktby 2023-09-28 03:45:13 Re: Set enable_seqscan doesn't take effect?