RHINENG-10032: fix repack job db user

[Dugowitch]

Secure Coding Practices Checklist GitHub Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[jira-linking]

Referenced Jiras:
https://issues.redhat.com/browse/RHINENG-10032

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.06%. Comparing base (45c6c36) to head (2aea703).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1479      +/-   ##
==========================================
+ Coverage   65.03%   65.06%   +0.02%     
==========================================
  Files         114      114              
  Lines        7877     7877              
==========================================
+ Hits         5123     5125       +2     
+ Misses       2217     2215       -2     
  Partials      537      537              

Flag	Coverage Δ
unittests	65.06% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[psegedy]

it might be possible that this won't help because admin user is probably not a superuser and the option to use regular user seems broken in pg_repack reorg/pg_repack#223
Can we use default postgres user? Try to look at how db migrations are performed, I think we're using the superuser there

[MichaelMraka]

According to reorg/pg_repack#201 you may need to use pg_repack -k .
Edit: I see there is --no-superuser-check.