pg.ddx.io  pgpartman/pg_partman GitHub issues and pull requests  
help / color / mirror / Atom feed
From: keithf4 (@keithf4) <noreply+keithf4@github.com>
To: pgpartman/pg_partman <noreply+pgpartman-pg_partman@github.com>
Subject: Re: [pgpartman/pg_partman] discussion #877: Full table scan of default partition during partman maintenance (ATTACH PARTITION)
Date: Thu, 29 Oct 2026 17:29:54 +0000
Message-ID: <gh-pgpartman-pg_partman-877-dc19274028@github.com> (raw)
In-Reply-To: <gh-pgpartman-pg_partman-877@github.com>
References: <gh-pgpartman-pg_partman-877@github.com>

You're saying here that the data is arriving late. I would assume this means the data has timestamps that are in the past, not the future? If that's the case, are you dropping older tables via retention? If so, ensure your retention window is longer than the window of time you expect late data. If this is data that is even older than you started your partition set for, then I'd just see about making as many older tables manually as you'd need to cover that window.

If you're talking about timestamp values in the the future, then set your premake window to account for the expected window of future data.

You could also re-evaluate your partition interval as well to make it larger so each table can cover a larger period of time.

If you can give an example of your table's schema along with the `part_config` entry for it, I might be able to help a bit more.

view thread (3+ messages)  latest in thread

Message-ID: <gh-pgpartman-pg_partman-877-dc19274028@github.com>
Permalink:  ../gh-pgpartman-pg_partman-877-dc19274028@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox