Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vWMup-0002jO-2h for pgsql-general@arkaria.postgresql.org; Thu, 18 Dec 2025 22:56:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vWMun-004WiG-1l for pgsql-general@arkaria.postgresql.org; Thu, 18 Dec 2025 22:56:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vWMun-004Wi7-0N for pgsql-general@lists.postgresql.org; Thu, 18 Dec 2025 22:56:09 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vWMul-001UmG-0S for pgsql-general@postgresql.org; Thu, 18 Dec 2025 22:56:09 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-3e3dac349easo1051788fac.2 for ; Thu, 18 Dec 2025 14:56:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1766098564; x=1766703364; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ih1gK5L2mv8/lWzC+yISICSaODfvygLyin/hK8xsas4=; b=lCg3zBs2BFGudLE4+tZFGKxLv9aurQR98YE1hd25not/CpHEL7k4Qmxt+IgvWQQRJX los0VqAQpTyRKQSOPRC8SoTiksZ70+DMBn2Nh2ziVeCLQYvrzy9F4AfGrw2x3l70tyUN QlAJeUmqPX9ppLagEIlL5UiiTnegwKqpZWd64+4r7OSamgqJgaRHPHInrV9r2FtSicHG zckMqSqvwZdsr1Rw52reorWInqANIUIcWbGNC67y9atjbF+tGfKR2bHpE97utS9lLfB2 vcSu7z0PpjBdpCUtoJsc3DWxQrXKZfEbJntfF4GVyhfQoW6JO2jBj7iPAUx69aP4gKyn BK/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766098564; x=1766703364; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ih1gK5L2mv8/lWzC+yISICSaODfvygLyin/hK8xsas4=; b=UDotluFv+0iD45phLjpnk/ZqXpaPhveyUXWrUzXg4bOZouitZbM3FZOFEHqkktuTWm c9vT9cd56Nzugt6S4KE7Fcq5384tfhGShkbs8azXnYDqqRBzZAbbCgSOSkkOYeYRzTys rLTobK+fnloZjsRljsatx8v4Lh1/FR7Va18AgJiidx8kUQig7PkfIheztAZxIpIYofJl /sd+hH+OToyr9y+clgmp+DNtUUZrX5kaZ51dfFJtqNrrjQEG0h6Zc7SYKQ/CHtlqK71T 8G1YNtmdRTeviK7n0jXWbB3u+sFlcppJt8vjOKnHvs7yujX+F7Z8W55wxOMbsiMJq3pw wuxA== X-Gm-Message-State: AOJu0YzcVMSBawUMI0+rzaOS5Bk6DK8hrTVJgp+nh5a5ua2wbu0wgVb0 6v/uqZsxjq4vExAO8Zl3J+Xt+XP6R8kT1tIruy/FClxUIbtHehHl85LFBYvQSXrtn9fizOU9shC mnVF/g0jCpDRzTVP3h7gc1Y2Qz1daleugBA== X-Gm-Gg: AY/fxX6yx0AxQiTT6O/rg9ccW1mcjrNVbBrgh60M3aakNPJXi+zPY1vlrd5F0jZu3yU BzW/Ob/8NBdbavG+uZpiUK3pzRxAOJJ75GCYdAfAWzEQa6IizrVK8KBDOt3nJNa7eXTXNoGDANT I2MM1s27zxLFiZ/zXgn4Wtb7/69cZ2QQlizUY7JnxmfOkPXYzeTnKqOxpif5qXCASTWKllUlhCO ohzBnQTnK42CX0N9D9sIt0Ory3pTkGJ044pkyftb92Qp44kLTzXKfRmS/R7ICWxwGkIx/KH X-Google-Smtp-Source: AGHT+IE7e/a7vyFycBiGkK5+JIfbq9ei9LbII84LMuqM0/rKLFx+tBOzm6sfJ57kmsse8HfTgy7YnaKLC4DaKHC3BZ8= X-Received: by 2002:a05:6808:509f:b0:455:d4ee:bb2a with SMTP id 5614622812f47-457b2088d05mr665448b6e.5.1766098564447; Thu, 18 Dec 2025 14:56:04 -0800 (PST) MIME-Version: 1.0 References: <87bjjv1v96.fsf@gmail.com> In-Reply-To: From: Ron Johnson Date: Thu, 18 Dec 2025 17:55:53 -0500 X-Gm-Features: AQt7F2o688cLLQnzy2gH8fPN9dMEdpXtSxXMJVcvRKP3FMq8E_ZDqgZT2RItaXo Message-ID: Subject: Re: Dealing with SeqScans when Time-based Partitions Cut Over To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000928132064641ddb6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000928132064641ddb6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Dec 18, 2025 at 3:21=E2=80=AFPM David Rowley = wrote: > On Fri, 19 Dec 2025 at 08:55, Matthew Planchard > wrote: > > > How about just force seqscan off when the table is created? > > > ALTER TABLE SET (enable_seqscan =3D 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 partition= s > > 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. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000928132064641ddb6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Dec 18, 2025 at 3:21=E2=80=AFPM D= avid Rowley <dgrowleyml@gmail.co= m> 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=C2=A0 =3D= 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 partitio= ns
> 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.=C2=A0 I should have known that would be too easy.

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