From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | azhwkd <azhwkd(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: query locks up when run concurrently |
Date: | 2016-11-23 23:26:43 |
Message-ID: | c7f07192-c079-5858-d5c8-0dfeee474776@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/23/2016 01:47 PM, azhwkd wrote:
> Greetings!
>
> Yes I had a look at the logfiles but there is not a single logfile
> generated when I'm reproducing this issue.
We are talking about the Postgres logfile, correct?
I have to believe a log file exists, but maybe not entries at that time.
What are you logging settings?
> 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 foreign keys
> as they only contain calculated data and the source data is removed
> after some time.
> The trigger which calls the partition function below is defined as follows:
>
> create
> trigger group_history_trigger before insert
> on
> item_history for each row execute procedure
> group_history_partition_function()
This trigger is on the table item_history not group history, is that
correct?
If so how does the item_history table fit into this?
>
> Kind regards,
> Sebastian
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-11-23 23:28:26 | Re: query locks up when run concurrently |
Previous Message | Tom Lane | 2016-11-23 22:39:32 | Re: Query with large in clauses uses a lot of memory |