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

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over
Date: 2025-12-18 22:55:53
Message-ID: CANzqJaCzMGpNhDfD2uZCidGVKFtfrGX1K+C0u1o6_MKeqMob-A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 18, 2025 at 3:21 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

> 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.
>

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!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-12-19 07:43:06 Re: PQexecPrepared() question
Previous Message David Rowley 2025-12-18 20:21:41 Re: Dealing with SeqScans when Time-based Partitions Cut Over