Re: Query tool bombing out

Hi calle,

Did you check the Data output tab ? There must be a visible loader to show
the progress. Or, on the bottom right corner - "Waiting...." message ?

On Fri, Apr 29, 2022 at 4:25 AM Calle Hedberg <calle(dot)hedberg(at)gmail(dot)com>
wrote:

> Aditya,
>
> Here's a typical screenshot, but I am afraid it won't tell you much:
>
> [image: image.png]
> Session is idle, the execute icon greyed out, and there is nothing under
> messages after execution.
>
> Logs and sample data is more tricky, because the database has health data
> for well over a million people - not something I can just share or provide
> access to.
>
> My initial query was basically just to ask if anybody has experienced the
> query tool behaving in this way, and if yes if they figured out why....
>
> Regards
> Calle
>
> On Wed, 27 Apr 2022 at 06:13, Aditya Toshniwal <
> aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
>
>> Hi Calle,
>>
>> It would be helpful if you can provide some screenshots, log, sample data
>> and steps to reproduce at our end.
>>
>> On Wed, Apr 27, 2022 at 4:19 AM Calle Hedberg <calle(dot)hedberg(at)gmail(dot)com>
>> wrote:
>>
>>> Hi,
>>>
>>> For at least the last 6 months, I have observed an increased tendency
>>> for query tools tabs to bomb out without providing any data output and/or
>>> Message output. What I see has the following characteristics:
>>>
>>> 1.
>>> Whether I run a single script or multiple scripts (each terminated by
>>> semicolon) does not matter, and I have not been able to figure out any kind
>>> of pattern to these failures;
>>> 2.
>>> The majority of my update scripts relate to JSONB field updates, but not
>>> all;
>>> 3.
>>> The script run will bomb out after anywhere from 2 to 20 seconds;
>>> 4.
>>> There is no message output, the execute icon turns grey, and the
>>> connection status indicates "The session is idle and there is no current
>>> transaction";
>>> 5.
>>> The query tool tab is permanently disabled, and I have to close it and
>>> open a new tab to run the script again; Usually the script will then run
>>> normally, but sometimes I have to do it 2 or 3 times before success (for
>>> each round I have to close the disabled tab and open a new one);
>>> 6.
>>> Sometimes I find that the original script actually DID work (when
>>> running it again I get 0 updates even when I know there must be some),
>>> sometimes it has not actually updated anything. This indicates that the
>>> script execution sometimes bombs before it has even run or at least
>>> finished, sometimes it bombs out after finishing but before the result
>>> message is displayed;
>>> 7.
>>> Finally, note that these are standardised scripts, around 50 of them,
>>> that I run every 2-3 days to correct errors or missing values for client
>>> data (covid-19 vaccinations) captured on a daily basis. So there is nothing
>>> wrong with the scripts themselves - the problem is that pgadmin is somehow
>>> unable to finish many of them in some cases.
>>> 8.
>>> I see no similar problems when running the same scripts from the command
>>> line.
>>>
>>> Does anybody have a clue what the issue might be here?
>>>
>>> Best regards
>>> Calle
>>>
>>>
>>>
>>
>> --
>> Thanks,
>> Aditya Toshniwal
>> pgAdmin Hacker | Software Architect | *edbpostgres.com*
>> <http://edbpostgres.com>
>> "Don't Complain about Heat, Plant a TREE"
>>
>
>
> --
>
> *Carl-Anders (Calle) Hedberg*
>
> HISP
>
> Researcher & Technical Specialist
>
> Health Information Systems Programme – South Africa
>
> Cell: +47 41461011 (Norway)
>
> Iridium SatPhone: +8816-315-19119 (usually OFF)
>
> E-mail1: calle(at)hisp(dot)org
>
> E-mail2: calle(dot)hedberg(at)gmail(dot)com
>
> Skype: calle_hedberg
>

--
Thanks,
Aditya Toshniwal
pgAdmin Hacker | Software Architect | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"