Skip to content
This repository has been archived by the owner on Aug 12, 2022. It is now read-only.

fix: Issues when PG username is 'cloudquery' #371

Merged
merged 1 commit into from
Jun 24, 2022
Merged

fix: Issues when PG username is 'cloudquery' #371

merged 1 commit into from
Jun 24, 2022

Commits on Jun 24, 2022

  1. fix: Issues when PG username is 'cloudquery'

    Before this fix, cloudquery misbehaved when the PG username was named 'cloudquery'.
    It created tables in the 'cloudquery' schema instead of the 'public' schema.
    This happened because the search path was  '"$user", public', which means it depended on the username.
    
    This fix, upon connection to PG, will change serach_path to 'public' only, i.e. not dependent on username (which is way more predictable).
    
    This won't impact us explicitly accessing the 'cloudquery' schema via 'cloudquery.<table-name>', which is what we do when we actually need the 'cloudquery' schema.
    shimonp21 committed Jun 24, 2022
    Configuration menu
    Copy the full SHA
    08457cd View commit details
    Browse the repository at this point in the history