public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Rowley <[email protected]>
To: Matthew Planchard <[email protected]>
Cc: Ron Johnson <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
Date: Fri, 19 Dec 2025 09:21:41 +1300
Message-ID: <CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ@mail.gmail.com> (raw)
In-Reply-To: <CAHncFmSsXwmLCKs-ySFWe=gjb=rSaSsVZQV6hJuDczhLixidqA@mail.gmail.com>
References: <[email protected]>
<CANzqJaAXhYwR6vHzm_DqnxmWk8QCYxEmhs_JeZ+w3F+rx09xSw@mail.gmail.com>
<CAHncFmSsXwmLCKs-ySFWe=gjb=rSaSsVZQV6hJuDczhLixidqA@mail.gmail.com>
On Fri, 19 Dec 2025 at 08:55, Matthew Planchard <[email protected]> wrote:
> > How about just force seqscan off when the table is created?
> > ALTER TABLE <table_partition> SET (enable_seqscan = off);
>
> I didn't know this could be set on the table level! Our partitions are
> created by partman, but we have a nightly job that does maintenance
> stuff that could go through and update this setting on future partitions
> before they come into use. I'm always hesitant to mess
> too much with the planner, but this might be the ticket.
You thought correctly. There's no such reloption.
David
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
In-Reply-To: <CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox