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

From David Rowley
Subject Re: Dealing with SeqScans when Time-based Partitions Cut Over
Date
Msg-id CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ@mail.gmail.com
Whole thread Raw
In response to Re: Dealing with SeqScans when Time-based Partitions Cut Over  (Matthew Planchard <msplanchard@gmail.com>)
Responses Re: Dealing with SeqScans when Time-based Partitions Cut Over
List pgsql-general
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



pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
Next
From: Ron Johnson
Date:
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over