| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "Bawol, Brian" <brian(dot)bawol(at)freightverify(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org, pgadmin-support(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Date: | 2019-02-07 20:28:38 |
| Message-ID: | 25473.1549571318@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2019-02-08 04:24:54 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Tom Lane | 2019-02-07 20:23:21 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2019-02-08 04:24:54 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| Previous Message | Tom Lane | 2019-02-07 20:23:21 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |