Had the same issue, as its a shared space on AWS with 1000 other DBs.
pgAdmin 3
'dback447'
pgAdmin 4
Same as above, but on step 3 do not use quotes, just the plain DB name. E.g dback447
pgAdmin 4 version 6.1
Same as above, but press Tab after entering the name of each database. Commas or spaces take your string as a name of one single database.
And you have to press Tab even if you want to type only one database name, otherwise the Save button ignores your changes.
pgAdmin 4 does not contain the 'DB Restriction' which is the only reason I am not using it, forcing me to settle for pgAdmin 3.
There was a ticket opened up to add this functionality in pgAdmin 4 ... https://redmine.postgresql.org/issues/1918
The latest version of pgAdmin 4 (2.0) has the DB restriction property too in the "Advanced" tab of the server connection property, much the same as in pgAdmin 3. No quotes needed.
I had the same issue with only 10 other DBs and Matt Stevens' answer was only partly helpful ie at first it helped and then I got access to another DB on the same server.
I did all as described and it shoed no DB at all. In 'DB restriction' you type in the name of your databases enclosed in single quotes and separated by commas. E.g. 'db1', 'db2'.
Don't enclose in single quotes in pgAdmin 4.5, it will not work if you do.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With