ymore.
I took this one step further and left the locked up queries sitting there
for a day and they eventually finished. Who would have thought a ~2 second
query could blow up to ~20hrs.
rob stone schrieb am Fr., 25. Nov. 2016 um 02:34 Uhr:
On Thu, 2016-11-24 at 22:23 +0100, azhwkd wrote:
> I
Adrian Klaver schrieb am Do., 24. Nov. 2016 um
22:34 Uhr:
> On 11/24/2016 01:23 PM, azhwkd wrote:
> > It should not be possible because a group does not return to the
> > update pool before the update hasn't finished.
>
> So what is this 'update pool' and wh
ew updates go through and eventually it will
lock up completely and sometimes it locks up immediately - always with
heap_hot_search_buffer using ~20 of all CPU time on the system.
2016-11-24 19:14 GMT+01:00 Adrian Klaver :
> On 11/23/2016 10:41 PM, azhwkd wrote:
>>
>> The group ID i
t;,"hour")
)
WITH (
OIDS=FALSE
);
Kind regards,
Sebastian
2016-11-24 0:28 GMT+01:00 Adrian Klaver :
> On 11/23/2016 01:52 PM, azhwkd wrote:
>>
>> Greetings!
>>
>> The parallel calls should not be working on the same row. Each query
>> services a different gr
e (item_history is a test table I created yesterday while
trying things which is exactly the same as group_history just a
different name).
The trigger on the group_history table is exactly the same though,
except for the table name.
Kind regards,
Sebastian
2016-11-24 0:26 GMT+01:00 Adrian Klaver :
>
Greetings!
The parallel calls should not be working on the same row. Each query
services a different group ID on it's own and there is no overlap.
Kind regards,
Sebastian
Tom Lane schrieb am Mi., 23. Nov. 2016 um 17:47 Uhr:
> azh...@gmail.com writes:
> > I have a query which if run alone usua
Greetings!
Yes I had a look at the logfiles but there is not a single logfile
generated when I'm reproducing this issue.
Concerning locks I used there queries at
https://wiki.postgresql.org/wiki/Lock_Monitoring and they came up empty.
The group_history table and its sub-tables do not have any fore
Greetings!
I'm using postgres version 9.5.5 on a ubuntu 16.04.1 server
installation which was installed through apt-get.
I have a query which if run alone usually completes in about 300ms.
When run in my application this query constantly locks up and bogs
down all connections of the connection po
Greetings!
I'm using postgres version 9.5.5 on a ubuntu 16.04.1 server
installation which was installed through apt-get.
I have a query which if run alone usually completes in about 300ms.
When run in my application this query constantly locks up and bogs
down all connections of the connection po
