| /dports/databases/postgresql96-server/postgresql-9.6.24/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-contrib/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql96-pltcl/postgresql-9.6.24/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql96-plpython/postgresql-9.6.24/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-plperl/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-pltcl/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-client/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-client/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-docs/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-plpython/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-docs/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-contrib/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-plpython/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-plperl/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-server/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql10-server/postgresql-10.19/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql12-contrib/postgresql-12.9/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql12-client/postgresql-12.9/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql11-pltcl/postgresql-11.14/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql14-pltcl/postgresql-14.1/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql14-server/postgresql-14.1/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql96-client/postgresql-9.6.24/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql14-contrib/postgresql-14.1/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql14-plpython/postgresql-14.1/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|
| /dports/databases/postgresql14-plperl/postgresql-14.1/src/backend/access/heap/ |
| H A D | README.tuplock | 26 LockTuple()
32 is provided by LockTuple(). However, at most one tuple-level lock will
35 do LockTuple as well, if there is any conflict, to ensure that they don't
41 case, we skip the LockTuple() call even when there are conflicts, provided
45 be waiting on the LockTuple() call to upgrade to the stronger lock level, and
46 another session that has already done LockTuple() and is waiting for the first
|