| From: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "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-08 04:24:54 |
| Message-ID: | CAG7mmoz+71Uk1FWGr40jk8mmYOkNuFGRHhjyrmgzXr2V4avJRQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support pgsql-admin |
On Fri, Feb 8, 2019 at 1:58 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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';
>
Thanks for the solution - Tom.
We will fix that in that in pgAdmin.
-- Thanks, Ashesh
>
> This is depressingly lacking in safe schema-qualification, btw.
>
> regards, tom lane
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashesh Vashi | 2019-02-08 04:52:53 | Re: Cannot connect to Replication Slave with the new Version 4.2 of PGAdmin4 |
| Previous Message | Tom Lane | 2019-02-07 20:28:38 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremiah Bauer | 2019-02-08 15:47:28 | Postgres Database Disk Usage |
| Previous Message | Tom Lane | 2019-02-07 20:28:38 | Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances |