MIME-Version: 1.0
References: <87bjjv1v96.fsf@gmail.com> <CANzqJaAXhYwR6vHzm_DqnxmWk8QCYxEmhs_JeZ+w3F+rx09xSw@mail.gmail.com>
 <CAHncFmSsXwmLCKs-ySFWe=gjb=rSaSsVZQV6hJuDczhLixidqA@mail.gmail.com>
In-Reply-To: <CAHncFmSsXwmLCKs-ySFWe=gjb=rSaSsVZQV6hJuDczhLixidqA@mail.gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
Date: Fri, 19 Dec 2025 09:21:41 +1300
Message-ID: <CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ@mail.gmail.com>
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
To: Matthew Planchard <msplanchard@gmail.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>, pgsql-general <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ%40mail.gmail.com>
Precedence: bulk

On Fri, 19 Dec 2025 at 08:55, Matthew Planchard <msplanchard@gmail.com> 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