Skip to content

Conversation

jw1u1
Copy link
Contributor

@jw1u1 jw1u1 commented Sep 9, 2025

Incorrectly configured tables have previously led to the termination of the procedure
Untested for id based partitioning!

@keithf4 keithf4 self-assigned this Sep 23, 2025
@keithf4 keithf4 added this to the Next Patch milestone Sep 23, 2025
@keithf4 keithf4 merged commit 7079042 into pgpartman:development Oct 14, 2025
@keithf4
Copy link
Collaborator

keithf4 commented Oct 15, 2025

So this was a noble attempt to try and catch exceptions and move on to other partition sets, but there's far too many places that are going to be needed to try and catch issues. Testing this myself I kept running into more and more places that would need to be caught, especially when calling other functions. Rather than have some of these caught and not others, I'd rather not have this being handled at all so there's not some expectation that all the other places need to be caught and handled as well.

Thank you for the attempt, but I'll be undoing this commit on my end.

@keithf4
Copy link
Collaborator

keithf4 commented Oct 15, 2025

If there is some issue with partition maintenance not working with a specific table, the automatic_maintenance column in part_config can be set to off and the calls to run_maintenance() with no argument will skip those partition sets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants