Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eyrHv-0000Qe-8H for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Mar 2018 03:53:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1eyrHu-0004Jr-0d for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Mar 2018 03:53:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <911zrfelix@gmail.com>) id 1eyrHt-0004Je-NU; Thu, 22 Mar 2018 03:53:13 +0000 Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from <911zrfelix@gmail.com>) id 1eyrHm-0001XU-TR; Thu, 22 Mar 2018 03:53:13 +0000 Received: by mail-wm0-x235.google.com with SMTP id l16so13501604wmh.3; Wed, 21 Mar 2018 20:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=V+UACI73Gz8kB6XaS9SCNdhn8p8Ybe9c4mmMUwge4R0=; b=JUY6OvJoByEGqCEa+X8sDiIJdnNCW/+U+b8K37IisiXd92nV9qd55s5AWhfE3NvcUq v1rPuHa+2SNbWYSPWlGY4BUNG0dMVBH9wq8WiBJbwlwTRkjmBkh+dBdVTbeDhjAC8iJE PkdtOuxMdd1qkNes695viuVdcLhFLSs9tX1htKKxIAb9OycJiXX0IamWGV7SssQBDGUC SQ+osi0MyLdKeEqEg1SsS8n+8Iy5t2iTENxYQ7s+9ZrfFTSdyBeaddc5eyCbjnr5Ns8h VhlamBkmGqv7mW6qgCKSRKVT+5eo09a/HQi23CoARTidct6eSZ2RTw0b+85MbXMnkTBz /RxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=V+UACI73Gz8kB6XaS9SCNdhn8p8Ybe9c4mmMUwge4R0=; b=M7q/VVhND9VSvUD3YJfz66sdhrJjjrapFDf/fg7YWIzP1iHLnMHbO0i9jGZTUNlqSJ P7wAz+3luF8ZT8xK4QL3lBWCHxfTkvSsGM73aXrm9PKTwvU+Cp8SCy16p3ilnxfMwlI9 PfauE0oYM78WomDq876xbZEuHbAoiiX0LTPu3zlTlTyMGKaiB24s3FoggSIJHDn2ZO3P /826fLQXnUpP/oKpD+JCX1rVUdPD4CAh+2760tvZ1NPbBAD53S6lZn6dtqfYrz0GLPxS CAbfqs7UIDAmqTQdeoaVAf3yrQNU1lkpoq1oQDWh0FtIDlSqTi1Kfk6bZTUQPkzKFHkN xLfQ== X-Gm-Message-State: AElRT7FsIpen7xtBtPDZK8x6f8X1897kIUSHex7gtjEIcZ2SXFvrBVbB Dfm3ClVGHjfn31z0fhPaS8CPHQSLfv41//G8mW8Dgw== X-Google-Smtp-Source: AG47ELv0j/dTFg5D4/m+QMWO6TRyJWDPkBGYFxfAI+ZvOQzdX/VHHWr6q08OEH7j39mo9DiBGj9No/6g+jBzDjWhka0= X-Received: by 10.28.212.136 with SMTP id l130mr2722426wmg.15.1521690785510; Wed, 21 Mar 2018 20:53:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.152.148 with HTTP; Wed, 21 Mar 2018 20:53:04 -0700 (PDT) From: RUI ZHU <911zrfelix@gmail.com> Date: Thu, 22 Mar 2018 11:53:04 +0800 Message-ID: Subject: Reports of Bugs To: pgsql-bugs@lists.postgresql.org, pgsql-gui-dev@lists.postgresql.org Content-Type: multipart/alternative; boundary="001a11469912ba7bd70567f83e1b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a11469912ba7bd70567f83e1b Content-Type: text/plain; charset="UTF-8" Hi PostgreSQL communities, I am a heavy PostgreSQL user, and I love PostgreSQL very much. However, I would like to report something that shall be improved: (I am using pgAdmin 4 v2.1 for PostgreSQL 10 in Windows 10) 1. Everything is fine before the version of pgAdmin 4 v2.0 but problems comes from pgAdmin 4 v2.0. I come across the errors of pgAdmin 4 v2.1 everyday that the pgAdmin stops and turns off with unclear reasons. This problem occurs in different computers that shall be tackled in a timely manner. 2. The design of "waiting for the query execution to complete..." is good to avoid duplicated or conflict executions of queries. However, I can do nothing to review and edit my SQL codes but wait for the completion. One way to avoid the "waiting for the query execution to complete..." is not pressing the saving bottom and pressing the execution bottom. When "waiting for the query execution to complete..." pops up, press the saving bottom, then I can review and edit my codes with the SQL execution. It would be good if we remove the "waiting for the query execution to complete...". 3. When I press "Ctrl+v" to save the .sql file, the save bottom does not turn to the gray color that I am not sure my file is saved successfully or not. Then, I have to use the mouse to press the save bottom, which is not good and not convenient. 4. I cannot increase the font size of the SQL codes, which is needed by a lot of users. 5. When the run time is over 1 min, Messages and Query History only show the minute without the second information. I need the second information urgently because it can tell me the efficiency of my SQL code more accurately. Executions of a SQL statement takes 1 min vs. 1 min 50 secs are significantly different. Even though I can put the query into a function and calculate the total execution time accurately, it is still not convenient at all. Thus, wish the seconds information can be added in the next version. Wish to get your feedback and these problems can be solved. I sincerely thank you all very much for your contribution for the PostgreSQL! Best Regards, Felix --001a11469912ba7bd70567f83e1b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi PostgreSQL communities,

I am a heavy= PostgreSQL user, and I love PostgreSQL very much. However, I would like to= report something that shall be improved:

(I am using pgAdmin 4 v2.1 for PostgreSQL 10 in W= indows 10)

1. Everything is fine before the version of pgAdmin 4 v2.0 but problem= s comes from pgAdmin 4 v2.0. I come across the errors of pgAdmin 4 v2.1 eve= ryday that the pgAdmin stops and turns off with unclear reasons. This probl= em occurs in different computers that shall be tackled in a timely manner.<= /div>

2. The design of "waiting for the query execu= tion to complete..." is good to avoid duplicated or conflict execution= s of queries. However, I can do nothing to review and edit my SQL codes but= wait for the completion. One way to avoid the=C2=A0 "waiting for the query execution to complete= ..."=C2=A0is not pressing the saving bottom and pressing the ex= ecution bottom. When=C2=A0=C2=A0"waiting for= the query execution to complete..." pops up, press the saving bottom,= then I can review and edit my codes with the SQL execution. It would be go= od if we remove the=C2=A0 "waiting for the query execution to complete= ...".

3. When I press "Ctrl+v" to save the .sql file,= the save bottom does not turn to the gray color that I am not sure my file= is saved successfully or not. Then, I have to use the mouse to press the s= ave bottom, which is not good and not convenient.
<= span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm= all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma= l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te= xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(= 255,255,255);text-decoration-style:initial;text-decoration-color:initial;fl= oat:none;display:inline">
=
4. I cannot increa= se the font size of the SQL codes, which is needed by a lot of users.

=

<= /span>
Wish to get your feedback and these problems can be solved. I sincerely th= ank you all very much for your contribution for the PostgreSQL!

Best= Regards,

Felix





--001a11469912ba7bd70567f83e1b--