Re: Dealing with SeqScans when Time-based Partitions Cut Over

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Matthew Planchard <msplanchard(at)gmail(dot)com>
Cc: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
Date: 2025-12-18 20:21:41
Message-ID: CAApHDvoszp3fhsJQ759SkpYpJsn8ZcLXB26oR0sxXV-EavWKfQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 19 Dec 2025 at 08:55, Matthew Planchard <msplanchard(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-12-18 22:55:53 Re: Dealing with SeqScans when Time-based Partitions Cut Over
Previous Message David Rowley 2025-12-18 20:20:30 Re: Dealing with SeqScans when Time-based Partitions Cut Over