Skip to content

Conversation

jw1u1
Copy link
Contributor

@jw1u1 jw1u1 commented Sep 10, 2025

Prevent a mixture of partition owners that lead to permission issues and run_maintenance failures.
Skip Tables that are not owned by the current_role with a warning.

@jw1u1 jw1u1 changed the title skip and warn about role mismatch in run_maintenance skip and warn about role mismatch in Maintenance Functions Sep 12, 2025
@keithf4
Copy link
Collaborator

keithf4 commented Sep 23, 2025

Just wanted to say thank you for the updates you've done recently. I won't be able to get them in the next release that will hopefully be coming out soon, but I do plan on getting back to more frequent updates again and will review and try and get the ones you've been working on lately incorporated in future releases.

@keithf4 keithf4 self-assigned this Sep 23, 2025
@keithf4 keithf4 modified the milestones: 5.4, Next Patch Sep 23, 2025
AND c.relname = v_parent_tablename;

IF v_parent_owner != current_role THEN
RAISE EXCEPTION 'parent table % owner is % but current role is %', p_parent_table, v_parent_owner, current_role;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I don't think this is accounting for role inheritance/group membership. It's just looking to see if the name of the owner simply matches the name of the current role. If a role is a member of another role, it's considered an owner of all of the same objects.

Also doesn't account for if a superuser is running it, which should be able to succeed as well.

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