PG: Only list tables where schema has USAGE permission

[eradman]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• New Query Runner (Data Source)
• New Alert Destination
• Other

Description

This covers cases where partitioned tables are part of a schema that is not accessible by the current user.

How is this tested?

• Unit tests (pytest, jest)
• E2E Tests (Cypress)
• Manually
• N/A

Create a new schema then set up a data source for Redash with another, non-superuser role

CREATE SCHEMA xyz;

CREATE TABLE xyz.tab (
   id bigint GENERATED ALWAYS AS IDENTITY,
   ts timestamp NOT NULL
) PARTITION BY LIST ((ts::date));

CREATE TABLE xyz.tab_default PARTITION OF xyz.tab DEFAULT;

Related Tickets & Documents

#6988

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.74%. Comparing base (10a46fd) to head (c8fb833).
Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7000      +/-   ##
==========================================
- Coverage   63.85%   63.74%   -0.11%     
==========================================
  Files         161      162       +1     
  Lines       13082    13222     +140     
  Branches     1811     1866      +55     
==========================================
+ Hits         8353     8428      +75     
- Misses       4429     4474      +45     
- Partials      300      320      +20     

Files	Coverage Δ
redash/query_runner/pg.py	42.34% <ø> (-0.22%)	⬇️

... and 9 files with indirect coverage changes

[justinclift]

Eyeballing this, it makes good sense to me. 😄

[eradman]

Thanks @justinclift for the second set of eyeballs! Could not figure out how to write a meaningful test for this, so had to rely on manual testing.