mirror of
https://github.com/postgres/postgres.git
synced 2025-08-19 23:22:23 +03:00
pgindent run for 9.6
This commit is contained in:
@@ -395,7 +395,8 @@ _bt_check_unique(Relation rel, IndexTuple itup, Relation heapRel,
|
||||
* Check for a conflict-in as we would if we were going to
|
||||
* write to this page. We aren't actually going to write,
|
||||
* but we want a chance to report SSI conflicts that would
|
||||
* otherwise be masked by this unique constraint violation.
|
||||
* otherwise be masked by this unique constraint
|
||||
* violation.
|
||||
*/
|
||||
CheckForSerializableConflictIn(rel, NULL, buf);
|
||||
|
||||
|
@@ -813,8 +813,8 @@ btvacuumscan(IndexVacuumInfo *info, IndexBulkDeleteResult *stats,
|
||||
|
||||
/*
|
||||
* Check to see if we need to issue one final WAL record for this index,
|
||||
* which may be needed for correctness on a hot standby node when
|
||||
* non-MVCC index scans could take place.
|
||||
* which may be needed for correctness on a hot standby node when non-MVCC
|
||||
* index scans could take place.
|
||||
*
|
||||
* If the WAL is replayed in hot standby, the replay process needs to get
|
||||
* cleanup locks on all index leaf pages, just as we've been doing here.
|
||||
@@ -1025,13 +1025,13 @@ restart:
|
||||
if (ndeletable > 0)
|
||||
{
|
||||
/*
|
||||
* Notice that the issued XLOG_BTREE_VACUUM WAL record includes all
|
||||
* information to the replay code to allow it to get a cleanup lock
|
||||
* on all pages between the previous lastBlockVacuumed and this page.
|
||||
* This ensures that WAL replay locks all leaf pages at some point,
|
||||
* which is important should non-MVCC scans be requested.
|
||||
* This is currently unused on standby, but we record it anyway, so
|
||||
* that the WAL contains the required information.
|
||||
* Notice that the issued XLOG_BTREE_VACUUM WAL record includes
|
||||
* all information to the replay code to allow it to get a cleanup
|
||||
* lock on all pages between the previous lastBlockVacuumed and
|
||||
* this page. This ensures that WAL replay locks all leaf pages at
|
||||
* some point, which is important should non-MVCC scans be
|
||||
* requested. This is currently unused on standby, but we record
|
||||
* it anyway, so that the WAL contains the required information.
|
||||
*
|
||||
* Since we can visit leaf pages out-of-order when recursing,
|
||||
* replay might end up locking such pages an extra time, but it
|
||||
|
@@ -392,15 +392,15 @@ btree_xlog_vacuum(XLogReaderState *record)
|
||||
xl_btree_vacuum *xlrec = (xl_btree_vacuum *) XLogRecGetData(record);
|
||||
|
||||
/*
|
||||
* This section of code is thought to be no longer needed, after
|
||||
* analysis of the calling paths. It is retained to allow the code
|
||||
* to be reinstated if a flaw is revealed in that thinking.
|
||||
* This section of code is thought to be no longer needed, after analysis
|
||||
* of the calling paths. It is retained to allow the code to be reinstated
|
||||
* if a flaw is revealed in that thinking.
|
||||
*
|
||||
* If we are running non-MVCC scans using this index we need to do some
|
||||
* additional work to ensure correctness, which is known as a "pin scan"
|
||||
* described in more detail in next paragraphs. We used to do the extra
|
||||
* work in all cases, whereas we now avoid that work in most cases.
|
||||
* If lastBlockVacuumed is set to InvalidBlockNumber then we skip the
|
||||
* work in all cases, whereas we now avoid that work in most cases. If
|
||||
* lastBlockVacuumed is set to InvalidBlockNumber then we skip the
|
||||
* additional work required for the pin scan.
|
||||
*
|
||||
* Avoiding this extra work is important since it requires us to touch
|
||||
|
Reference in New Issue
Block a user