May I have a suggestion... The Postgres connector lists a bunch of tables - from INFORMATION_SCHEMA I suspect - but this includes tables the user has no access to. We get a "Permission denied" runtime error and the job crushes. We have to read the log and then exclude/unselect one by one these tables, which is a tremendous process when you have 100+ tables. My suggestion is check also if the user can SELECT data from the tables you display in the Connection setup. And either completely hide the inaccessible tables, or at least unselect them by default, and show them with a different gray color. But most people deny access to tables to a user because they don't want that user to transfer data - so we should not have them in the list, at all. And this may apply to any other database source connector, not just for Postgres.

@Cristian Scutaru this is a great suggestion, other user also had problem with Oracle (because Oracle create a lot of internal tables). Do you mind creating a Github issue to improve this step in Airbyte workflow 😃