(psycopg2.OperationalError) FATAL: database "public" does not exist

[witwall]

Make sure these boxes are checked before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if any
• I have reproduced the issue with at least the latest released version of superset
• I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

0.15.0

Expected results

Show the result of SQL

Actual results

(psycopg2.OperationalError) FATAL: database "public" does not exist

Steps to reproduce

access PostgreSQL through SQL Lab,

[xrmx]

Does it work if you don't specify the schema?

[witwall]

@xrmx does not work, but preview works sometime

[mistercrunch]

Does it work if you SELECT ... FROM activity instead of public.activity?

[witwall]

it works no matter

SELECT *
FROM public.vintage LIMIT 100

or

SELECT *
FROM vintage LIMIT 100

just if I did not select any schema from let panel.

[sanjayobla]

I can confirm that I'm facing the same issue. If I choose the schema explicitly in the left pane and try to query a table with either

SELECT * FROM <schema_name>.<table_name>
or
SELECT * FROM <table_name>
I get the error
(psycopg2.OperationalError) FATAL: database <schema_name> does not exist

If I don't choose the schema name from the drop down and try to do
SELECT * FROM <schema_name>.<table_name>, everything works fine.

[Pixelartist]

Hello,

+1 - I am having the same issue, running superset in docker.

[mistercrunch]

Is there a full stacktrace from the server logs?

[mistercrunch]

Most likely the issue is around confusion between the database and schema "namespacing" in Postgres. Databases have different semantics in that area on how they name these logical groups (database, schema, owner) and how many levels of them they have, and SQLAlchemy takes a bit of a common denominator approach.

[mistercrunch]

Since we don't use Postgres at Airbnb I'd like for someone to step in and help fix this.

[huksley]

I have similar problem. Can`t deselect schema.

[sungjuly]

It's same/duplicated issue with #1558, and my PR was merged the last couple of days. You can use that feature correctly in the next release.

• Fixed a bug when querying with schema path to Redshift/Postgresql #1789

[mistercrunch]

0.17 is out!

[gustavodemari]

The problem continues on 0.17.3

[mistercrunch]

Notice: this issue has been closed because it has been inactive for 381 days. Feel free to comment and request for this issue to be reopened.