Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replicainstances

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replicainstances
Дата
Msg-id 20190207195605.GA14960@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances  ("Bawol, Brian" <brian.bawol@freightverify.com>)
Ответы 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  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-admin
On 2019-Feb-07, Bawol, Brian wrote:

> It looks like this is the query that occurs at the same time:
> 
> STATEMENT:  SET DateStyle=ISO; SET client_min_messages=notice;UPDATE
> pg_settings SET setting = 'escape'    WHERE name = 'bytea_output';SET
> client_encoding='UNICODE';
> 
> Does this help?

Ah, so pgadmin 4.2 is trying to set bytea_output, which is disallowed;
the reason it says "cannot execute SELECT" is that the UPDATE for the
view is turned into a "SELECT set_config()" by a view rule.

That makes sense.  This looks like a pgadmin bug ...

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


В списке pgsql-admin по дате отправления:

Предыдущее
От: Pepe TD Vo
Дата:
Сообщение: Re: insert aborted commands ignored
Следующее
От: Tom Lane
Дата:
Сообщение: Re: PgAdmin 4.2 unable to connect to AWS Postgres read-replica instances