Closed dpage closed 2 years ago
Comment migrated from Redmine: https://redmine.postgresql.org/issues/3973#note-1 Originally created by Ashesh Vashi at 2019-02-08 04:52:46 UTC.
Applied in changeset commit:eb3d3980e03df792afb7d53c9470827c29e6e4a2.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Status changed | New | In Testing |
Done Ratio changed | 0 | 90 |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/3973#note-2 Originally created by Ashesh Vashi at 2019-02-08 04:54:28 UTC.
@Fahar - please test it with a read-only instance.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Assigned To changed | Ashesh Vashi | Fahar Abbas |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/3973#note-3 Originally created by Akshay Joshi at 2019-02-08 05:36:40 UTC.
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Sprint changed | EDB Sprint 33 |
Comment migrated from Redmine: https://redmine.postgresql.org/issues/3973#note-4 Originally created by Fahar Abbas at 2019-02-11 09:13:41 UTC.
This is Resolved in with remote server and user is able is connect with AWS read-replica instance successfully and i tested Backup Restore, View/data, drop objects, query tool windows and all major functionalities.
Tested Build: https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/2019-02-11/
Redmine ticket header update:
Name | Old Value | New Value |
---|---|---|
Status changed | In Testing | Resolved |
Done Ratio changed | 90 | 100 |
Issue closed on Redmine.
Issue migrated from Redmine: https://redmine.postgresql.org/issues/3973 Originally created by Ashesh Vashi at 2019-02-08 04:39:25 UTC.
As per the following mail archive, user is not able to connect the readonly-only instance any more. Reference: https://www.postgresql.org/message-id/CAF56UXJbZqmpt4Cgcqz%3DyyEt_X9kfQTfN9ug_KNLEBDX%2B9z9hw%40mail.gmail.com
It is regression introduced to support older version of server (i.e. Updating 'bytea_output' settings using the update command). commit-id: d92368f8e5a508715afdda3695eebd5029732978
In order to fix the issue Tom suggested to use set_config(...) function instead of UPDATE statement @ https://www.postgresql.org/message-id/25473.1549571318%40sss.pgh.pa.us.