Re: Dealing with SeqScans when Time-based Partitions Cut Over - Mailing list pgsql-general

From Ron Johnson
Subject Re: Dealing with SeqScans when Time-based Partitions Cut Over
Date
Msg-id CANzqJaCzMGpNhDfD2uZCidGVKFtfrGX1K+C0u1o6_MKeqMob-A@mail.gmail.com
Whole thread Raw
In response to Re: Dealing with SeqScans when Time-based Partitions Cut Over  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-general
On Thu, Dec 18, 2025 at 3:21 PM David Rowley <dgrowleyml@gmail.com> wrote:
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.

Ah well.  I should have known that would be too easy.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
Next
From: Igor Korot
Date:
Subject: Re: PQexecPrepared() question