Keith Fiske

So I can see how it's tricky with the current system. And even with the omnipitr setup, you would need the archive_command to be going to a different location to...

Just to let you know, I tried looking into this to see if it was easy to add those other columns in. Unfortunately, this takes some internals knowledge I don't...

I'll try to investigate this when I have a chance. Or if anyone else wants to work on committing the feature, I'm open to that as well.

Not sure I'll have the time to get to this myself until my next major code review for 5.0 later this year/early next year. If anyone else can contribute code...

Initially I thought the `p_start_partition` parameter would handle that, but apparently it still started at zero. I'll look into it when I have a chance or if you'd like to...

I think one issue with this that I'm still unsure of is do you need that offset just for the first partition or do you need that offset to continue...

Ok. Just wanted some clarification. Thanks!

Marking this as a feature to look into for 5.0. If I get a chance to look at it before then I will try.

pg_partman is based around the partitioning pattern of a range, not individual values. The upper and lower values for each child table must be different. I ran into issues even...

So went back and looked at why I was having issues with this before. It wasn't so much the constraints themselves on the child tables, it was the maintenance runs...