Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commita968659

Browse files
committed
We no longer need a snapshot set after opening the finishing transaction: this
is redundant because autovacuum now always analyzes a single table pertransaction.
1 parent49639a7 commita968659

File tree

1 file changed

+1
-10
lines changed

1 file changed

+1
-10
lines changed

‎src/backend/commands/vacuum.c

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
*
1414
*
1515
* IDENTIFICATION
16-
* $PostgreSQL: pgsql/src/backend/commands/vacuum.c,v 1.367 2008/03/14 17:25:58 alvherre Exp $
16+
* $PostgreSQL: pgsql/src/backend/commands/vacuum.c,v 1.368 2008/03/19 14:18:21 alvherre Exp $
1717
*
1818
*-------------------------------------------------------------------------
1919
*/
@@ -482,15 +482,6 @@ vacuum(VacuumStmt *vacstmt, List *relids,
482482
* PostgresMain().
483483
*/
484484
StartTransactionCommand();
485-
486-
/*
487-
* Re-establish the transaction snapshot. This is wasted effort when
488-
* we are called as a normal utility command, because the new
489-
* transaction will be dropped immediately by PostgresMain(); but it's
490-
* necessary if we are called from autovacuum because autovacuum might
491-
* continue on to do an ANALYZE-only call.
492-
*/
493-
ActiveSnapshot=CopySnapshot(GetTransactionSnapshot());
494485
}
495486

496487
if (vacstmt->vacuum&& !IsAutoVacuumWorkerProcess())

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp