Re: Set enable_seqscan doesn't take effect?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: jacktby jacktby <jacktby(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, andres(at)anarazel(dot)de
Subject: Re: Set enable_seqscan doesn't take effect?
Date: 2023-09-28 13:57:15
Message-ID: ZRWGO3EjflQ+ost3@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 28, 2023 at 03:38:28PM +0800, jacktby jacktby wrote:
> > 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.

I think you might find our IRC channel a more natural fit for getting
your questions answered:

https://www.postgresql.org/community/irc/

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kuwamura Masaki 2023-09-28 14:17:46 Re: Clarify where the severity level is defined
Previous Message Vik Fearing 2023-09-28 13:50:58 Re: Allow deleting enumerated values from an existing enumerated data type