| From: | AI Rumman <rummandba(at)gmail(dot)com> |
|---|---|
| To: | Douglas J Hunley <doug(dot)hunley(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Whats is lock type transactionid? |
| Date: | 2014-07-17 23:08:48 |
| Message-ID: | CAGoODpdqSuY==HVQyNNT4qFZuBZHN7jTRviWNg5PztEZ1L_GOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes. But as we are using bind variables, we are not able to get the ID of
the tuple.
On Thu, Jul 17, 2014 at 2:08 PM, Douglas J Hunley <doug(dot)hunley(at)gmail(dot)com>
wrote:
>
> On Thu, Jul 17, 2014 at 12:54 PM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
>
>> I am experiencing lock contention on one single UPDATE statement at a
>> certain time in whole day. This is a small table to UPDATE.
>> My suspect is we are facing it for one specific ID.
>> Could you please let me know how can I identify the tuple.
>>
>
> Have you tried the lock monitoring queries on
> http://wiki.postgresql.org/wiki/Lock_Monitoring yet by chance?
>
>
>
> --
> Douglas J Hunley (doug(dot)hunley(at)gmail(dot)com)
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prabhjot Sheena | 2014-07-17 23:26:20 | Re: Checkpoint_segments optimal value |
| Previous Message | Lists | 2014-07-17 22:50:12 | Detect streaming replication failure |