You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when querying pg_views, redshift coerces materialized views to be of relkind='v', so the below case statement is not relevant to Redshift at all. I wish that Redshift wouldn't do this, but I'll take as a consolation prize that the redshift python connector not have coded references to relkind='m'
Hi @dataders , thank you for taking the time to open this issue as well as the associated pull request. Given we align these metadata queries across all of our Redshift drivers, we will need to discuss this with the Redshift team before making any changes.
If you can please provide the following information to aid our team's discussion of this issue:
What impact is seen by this case statement's presence?
Which version of Redshift server was in use when this was discovered?
when querying
pg_views
, redshift coerces materialized views to be ofrelkind='v'
, so the below case statement is not relevant to Redshift at all. I wish that Redshift wouldn't do this, but I'll take as a consolation prize that the redshift python connector not have coded references torelkind='m'
amazon-redshift-python-driver/redshift_connector/cursor.py
Line 927 in b2dde82
The text was updated successfully, but these errors were encountered: