PGAdmin4 2.1 OSX Query Tool - messages delayed by one execution

I'm noticing that when executing a batch with multiple statements, the messages returned by the second statement onwards are kept over to the next execution and appear before the first message from the new batch. Steps to reproduce: Compile the following function which raises a notice: create or

Re: PGAdmin4 2.1 OSX bloat

Hi, As per Darren's post that's the exact steps I reproduced, the same goes for the download from the nag in the app when a new version is detected. I suspected something when the copy of the app in the DMG to the Applications folder took ages on an SSD.

Re: ERROR: invalid byte sequence for encoding

Hi, Here is the bugreport: https://redmine.postgresql.org/issues/3077 and here the patch: https://www.postgresql.org/message-id/cafohelfr8m52x13g6chstd6i+yepsikd8v696_qr7lj76s4...@mail.gmail.com Regards, André Am 16.01.2018 um 07:49 schrieb André Burkhardt: > Hi, > > thank you for your respons

Re: PGAdmin4 2.1 OSX bloat

As for where all that bloat is going, I took a minute of digging and found something interesting. /Volumes/pgAdmin\ 4/pgAdmin\ 4.app/Contents/Resources/web/pgadmin/static/js/generated/.cache/hard-source This one, single, "invisible" .cache directory in the application bundle is about 300MB b

Re: PGAdmin4 2.1 OSX bloat

On 2018-02-21 8:54 PM, fahar wrote: The application size of pgAdmin4 is 184.5MB on MAC 10.13 machine and it's not reproducible, can you please share the exact steps so we can find the actual root-cause of this behavior. I completely verify what iPeel said. A PgAdmin4 2.0 OSX is 403.4MB and ver

Re: PGAdmin4 2.1 OSX bloat

Screen_Shot_2018-02-22_at_9.png The application size of pgAdmin4 is 184.5MB on MAC 10.13 machine and it's not reproducible, can you please share the exact steps so we can find the actual root-cause of this behavio

PGAdmin4 2.1 OSX bloat

Hi, Installing V2.1 on OSX I noticed the size of the app on disk is 620MB! V2.0 is quite large at 420MB but a bloat of 200MB over one release is quite large. Is the increase justified or has something crept in? -- Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f21916