PGAdmin 4 Bug on Run Query

2017-07-04 Thread Ng Liang Jie ???
Hi all,


I encounter a bug in pgadmin 4 while running query.

I am running ssh tunneling  and forwarding the port to 127.0.0.1. PgAdmin 4 
server connection's hostname is set to "localhost" and port is configured to 
the port being forwarded.

Connection to db is working fine BUT query execution is not responding and View 
data feature is not working.


However the issue seems solved if the hostname change to "127.0.0.1".


Thanks and Best Regards

Liang Jie


Sent from Outlook


Re: [pgadmin-support] No SQL errors visible in pgAdmin 4 1.5

2017-07-04 Thread Pawel Hadam
Hi Murtuza,

I have found a solution, and I needed to change in postgresql.conf this
line:

lc_messages = 'en_GB.UTF-8'

and leave the other 3 parameters as they were before, when I created the
database:

lc_monetary = 'Polish_Poland.1250'
lc_numeric = 'Polish_Poland.1250'
lc_time = 'Polish_Poland.1250'


It works now and I can see all messages in pgAdmin 4 as well.

It's also described here:

https://stackoverflow.com/questions/44195177/pgadmin-4-ver-1-5-no-error-messages

Thank you and kind regards
Pawel



On 9 June 2017 at 15:39, Murtuza Zabuawala <
murtuza.zabuaw...@enterprisedb.com> wrote:

> That is strange. I do not see any error in log file :(
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> On Fri, Jun 9, 2017 at 2:31 AM, Pawel Hadam  wrote:
>
>> Hi Murtuza,
>>
>> Thank you - I have followed those steps and please find attached the
>> log file and the config files.
>>
>> The SQL I run was:
>>
>> select * from non_existing_table;
>>
>> and you can see it in line #2462 of the log file.
>>
>> I hope it helps.
>>
>> Thank you and kind regards
>> Pawel
>>
>>
>> On 8 June 2017 at 14:00, Murtuza Zabuawala
>>  wrote:
>> > Hi Pawel,
>> >
>> > I am not able not find any entry for your queries in log file, Can you
>> turn
>> > of the dashboard graphs for a while and then try to re-produce the
>> issue.
>> >
>> > Steps to turn of the graphs,
>> > 1) Goto File menu --> Preferences --> Dashboards --> Graphs
>> > 2) Provide a rate value as 123456789 in all 5 inputs
>> > 3) Click Ok
>> > 4) close pgadmin4
>> > 5) Delete the old log file
>> > 6) start pgadmin4
>> > 5) Re-produce the issue
>> >
>> > and send us this newly created log file.
>> >
>> > Again start the graphs,
>> > 1) Goto File menu --> Preferences --> Dashboards --> Graphs
>> > 2) Provide a rate value as 1 in all 5 inputs
>> >
>> > Thanks,
>> > Murtuza Zabuawala
>> > EnterpriseDB: http://www.enterprisedb.com
>> > The Enterprise PostgreSQL Company
>> >
>> > On Thu, Jun 8, 2017 at 3:07 AM, Pawel Hadam  wrote:
>> >>
>> >> Hi Murtuza/Dave,
>> >>
>> >> I have created now the "config_local.py" as well and I am also
>> >> attaching the output that now I can see in the Messages tab.
>> >>
>> >> I have run 2 SQLs:
>> >> 1) select * from items; -- an existing table
>> >> 2) select * from non_existing_table; -- a non-existing table
>> >>
>> >> Thanks and regards
>> >> Pawel
>> >>
>> >> On 7 June 2017 at 12:00, Murtuza Zabuawala
>> >>  wrote:
>> >> > Hello,
>> >> >
>> >> > Are you able to locate "config.py" in pgAdmin4 directory?
>> >> >
>> >> > If yes then create a new file named "config_local.py" along side
>> >> > "config.py"
>> >> > and add below config option in it,
>> >> > FILE_LOG_LEVEL = logging.DEBUG
>> >> >
>> >> > Restart pgAdmin4 and try to re-produce the issue again.
>> >> >
>> >> > --
>> >> > Regards,
>> >> > Murtuza Zabuawala
>> >> > EnterpriseDB: http://www.enterprisedb.com
>> >> > The Enterprise PostgreSQL Company
>> >> >
>> >> > On Wed, Jun 7, 2017 at 3:34 PM, Pawel Hadam 
>> wrote:
>> >> >>
>> >> >> Hi Murtuza,
>> >> >>
>> >> >> Thank you. I attached the empty log file to my previous email - this
>> >> >> is what was produced. Just an empty file.
>> >> >>
>> >> >> Also, I cannot find  "config_local.py" in my installation folder:
>> >> >> C:\Program Files (x86)\pgAdmin 4
>> >> >>
>> >> >> Thank you and kind regards
>> >> >> Pawel
>> >> >>
>> >> >>
>> >> >> On 7 June 2017 at 05:52, Murtuza Zabuawala
>> >> >>  wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > Without log file it very hard to trace the issue as this is not
>> >> >> > re-producible on our side.
>> >> >> > Are you sure that pgadmin4.log file is empty?
>> >> >> >
>> >> >> > Can you try again changing the logging configuration, add below
>> >> >> > config
>> >> >> > option in "config_local.py" (which is in pgAdmin4 installation
>> >> >> > directory),
>> >> >> >
>> >> >> > FILE_LOG_LEVEL = logging.DEBUG
>> >> >> >
>> >> >> > restart pgAdmin4 and re-produce the issue, check the log file for
>> any
>> >> >> > error.
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Regards,
>> >> >> > Murtuza Zabuawala
>> >> >> > EnterpriseDB: http://www.enterprisedb.com
>> >> >> > The Enterprise PostgreSQL Company
>> >> >> >
>> >> >> > On Wed, Jun 7, 2017 at 2:30 AM, Pawel Hadam 
>> wrote:
>> >> >> >>
>> >> >> >> Hi Murtuza,
>> >> >> >>
>> >> >> >> Thank you for your prompt answer. Those are the outputs for the
>> two
>> >> >> >> queries:
>> >> >> >>
>> >> >> >> *) UTF8
>> >> >> >> *) UNICODE
>> >> >> >>
>> >> >> >> (I can see the same output in pgAdmin III)
>> >> >> >>
>> >> >> >> And the log file is created but it's empty.
>> >> >> >>
>> >> >> >> I am not sure if this helps?
>> >> >> >>
>> >> >> >> Thanks and regards
>> >> >> >> Pawel
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> On 6 June 2017 at 07:28, Murtuza Zabuawala
>> >> >> >>  wrote:
>> >> >> >> > Hello,
>> >> >> >> >
>> >> >> >> > Can you provide output from given queries,
>> >