pgAdmin 4 commit: Fix ordering of VACUUM options which changed inPG11. - Mailing list pgadmin-hackers

From Dave Page
Subject pgAdmin 4 commit: Fix ordering of VACUUM options which changed inPG11.
Date
Msg-id E1ghX85-0003H4-RH@gothos.postgresql.org
Whole thread Raw
List pgadmin-hackers
Fix ordering of VACUUM options which changed in PG11. Fixes #3836

While we're at it, fix the JSON handling in the maintenance/backup/restore routes.

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=8fb340d23b00646e8bd5cdcbab11442b03bfa701
Author: Akshay Joshi <akshay.joshi@enterprisedb.com>

Modified Files
--------------
docs/en_US/release_notes_4_1.rst                                    | 1 +
web/pgadmin/tools/backup/__init__.py                                | 4 +---
web/pgadmin/tools/maintenance/__init__.py                           | 4 +---
web/pgadmin/tools/maintenance/templates/maintenance/sql/command.sql | 2 +-
web/pgadmin/tools/restore/__init__.py                               | 4 +---
5 files changed, 5 insertions(+), 10 deletions(-)


pgadmin-hackers by date:

Previous
From: pgAdmin 4 Jenkins
Date:
Subject: Jenkins build is back to normal : pgadmin4-master-python34 #852
Next
From: Dave Page
Date:
Subject: Re: [pgAdmin4][Patch] - RM 3836 VACUUM FULL FREEZE ANALYZE VERBOSEsyntax error on PostgreSQL 11