Add ability to select different schemas (rather than just public schema) in Postgres integration

[sjlogan]

I am attempting to use Airbyte to move data from a postgres db to a warehouse. The data I care about lives in a schema that is not the "public" schema. Airbyte currently only sees the public schema, thus I cannot use the tool to move my data.

When setting up a postgres integration in Airbyte, I would like to be able to see and select from a list of the schemas the postgres user I provided has access to before selecting the tables in that schema that I wish to migrate. Ideally, I would want to be able to select multiple schemas. Of course, this would also mean that Airbyte would have to be intelligent about writing data to their own schemas (or at least prepending schema names to target tables) when writing to the destination.

Stitch.io allows me to select a non-"public" schema as I am setting up a postgres source. If I select multiple schemas, it can prepend schema names to the target tables in the warehouse. They cannot write data to different target schemas in the target warehouse (without setting up multiple integrations), which would be the optimal solution.

Reach out if you have questions or if I can clarify anything.

[ChristopheDuong]

Adding conversation happening on slack around this use case:

[cgardens]

I believe the postgres source now supports multiple schemas. I think we just forgot to update this issue.

[davinchia]

Confirmed we support this today.