PostgreSQL multiple queries crash

[expired user #10627]'s profile image [expired user #10627] posted 7 years ago in General Permalink

Hi,

HeidiSQL always crashes when i run more than one query in PostgreSQL. This is happening since version 9.4, if i revert to 9.3 it works ok.

2 attachment(s):
  • Screenshot_1
  • Screenshot_2
[expired user #10631]'s profile image [expired user #10631] posted 7 years ago Permalink

Hello,

same thing here (v9.4.0.5125 against Postgres). I just would like to ad that clicking "continue" works fine for me, i.e. all expected tab results are shown and HeidiSQL continues working just fine. The error re-occurs each time multiple queries are executed (i.e. it is not a one time error)

I doubt it is related to the queries themselves as doing SELECT 1; SELECT 2; SELECT 3; does trigger the error.

Thanks, JG

ansgar's profile image ansgar posted 7 years ago Permalink

Never seen that before, but I'll try to reproduce that on Windows. Hopefully this is not another Wine issue, as these are most hard to fix. But it looks like some ordinary string list error when creating the tabs for your three query results.

ansgar's profile image ansgar posted 7 years ago Permalink

I failed to reproduce that here. No error, neither in "send queries one by one" nor in "send multiple queries in one go" mode. Shit.

We could probably see if the result tabs look different on your side. I attached a screeny from here.

1 attachment(s):
  • pg-multiquery-tabs
[expired user #10631]'s profile image [expired user #10631] posted 7 years ago Permalink

I failed to reproduce that here. No error, neither in "send queries one by one" nor in "send multiple queries in one go" mode. Shit.

We could probably see if the result tabs look different on your side. I attached a screeny from here.

Hello Ansgar,

Ah, the "send multiple queries in one go" mode works fine, great!, only "send queries one by one" triggers the error.

Our screens looks similar.

Paying attention to the timing, we can see that 1) all queries are executed, 2) result tabs are created/filled and tool-tips are generated for each tab 3) error is triggered and could be dismissed.

The number next to the Index Out Of Bound error is the number of queries, which sounds like at "-1" missing in the upper bound of the iterator

JG

1 attachment(s):
  • bugHeidiSQL

Please login to leave a reply, or register at first.