From: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
Cc: | Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: adding wait_start column to pg_locks |
Date: | 2021-02-02 13:00:47 |
Message-ID: | f9153182845e5584b954ab6f03514d13@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021-01-25 23:44, Fujii Masao wrote:
> Another comment is; Doesn't the change of MyProc->waitStart need the
> lock table's partition lock? If yes, we can do that by moving
> LWLockRelease(partitionLock) just after the change of
> MyProc->waitStart, but which causes the time that lwlock is being held
> to be long. So maybe we need another way to do that.
Thanks for your comments!
It would be ideal for the consistency of the view to record "waitstart"
during holding the table partition lock.
However, as you pointed out, it would give non-negligible performance
impacts.
I may miss something, but as far as I can see, the influence of not
holding the lock is that "waitstart" can be NULL even though "granted"
is false.
I think people want to know the start time of the lock when locks are
held for a long time.
In that case, "waitstart" should have already been recorded.
If this is true, I think the current implementation may be enough on the
condition that users understand it can happen that "waitStart" is NULL
and "granted" is false.
Attached a patch describing this in the doc and comments.
Any Thoughts?
Regards,
--
Atsushi Torikoshi
Attachment | Content-Type | Size |
---|---|---|
v6-0001-To-examine-the-duration-of-locks-we-did-join-on-p.patch | text/x-diff | 11.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2021-02-02 13:24:10 | Re: Single transaction in the tablesync worker? |
Previous Message | Mark Rofail | 2021-02-02 12:51:18 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |