Jeff Lambert

@petere here is my replication setup with 1.15.0 ``` CREATE USER pgbouncer WITH PASSWORD 'pgbouncer'; CREATE SCHEMA IF NOT EXISTS pgbouncer AUTHORIZATION pgbouncer; CREATE OR REPLACE FUNCTION pgbouncer.get_auth(p_usename TEXT) RETURNS...

Even simpler. I get the same problem using postgres/postgres and the following auth_query `SELECT usename, passwd FROM pg_shadow WHERE usename=$1`

Thank you @guybrowne and @2tvenom looks like I was overthinking it. So I was triggering the same error message as you, but it looks like the blame was on me.

you're right, I haven't had this issue since. I may have had a permission issue at the time. i.e. trying to track a table owned by 'postgres' but the connection...

This is still a problem in 2.11.2 This time trying to remove a database which has permissions granted to inherited roles 

The names `setup.sql` and `teardown.sql` might also be good As for use cases, how about sending a `pg_notify` broadcast that the DB is under "maintenance". In my case I want...

no I want a single pre/post for all migrations pre.sql migrations (100 files) post.sql

I have the same problem but with a `-` inside of an index name (hasura 2.13.0) I am unable to rename the offending constraint because it's not my database

Am I crazy or is it still not possible to provide custom names for functions? @0x777 @tirumaraiselvan

@tirumaraiselvan @rikinsk is there another issue for console support? or is this the one?