Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
| От | Tom Lane |
|---|---|
| Тема | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Дата | |
| Msg-id | 25473.1549571318@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances
Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Список | pgsql-admin |
I wrote:
>> This looks like a pgadmin bug ...
> Looking at it, I'm betting somebody thought this was a cute way to
> set bytea_output if it exists, without getting a failure on servers
> too old to have it. We added that in 9.0, so maybe it's not quite
> old enough to make it a moot point; but failing on RO servers is
> not nice either. Anyway, yeah, it's pgadmin's problem to fix.
Better idea:
select set_config('bytea_output','escape',false) from pg_settings where name = 'bytea_output';
This is depressingly lacking in safe schema-qualification, btw.
regards, tom lane
В списке pgsql-admin по дате отправления: