mirror of
https://github.com/postgres/postgres.git
synced 2025-05-01 01:04:50 +03:00
Remove unnecessary GetTransactionSnapshot() calls
In get_database_list() and get_subscription_list(), the GetTransactionSnapshot() call is not required because the catalog table scans use the catalog snapshot, which is held until the end of the scan. See table_beginscan_catalog(), which calls RegisterSnapshot(GetCatalogSnapshot(relid)). In InitPostgres, it's a little less obvious that it's not required, but still true I believe. All the catalog lookups in InitPostgres() also use the catalog snapshot, and the looked up values are copied while still holding the snapshot. Furthermore, as the removed FIXME comments said, calling GetTransactionSnapshot() didn't really prevent MyProc->xmin from being reset anyway. Discussion: https://www.postgresql.org/message-id/7c56f180-b9e1-481e-8c1d-efa63de3ecbb@iki.fi
This commit is contained in:
parent
7ec4b9ff80
commit
952365cded
@ -1799,18 +1799,9 @@ get_database_list(void)
|
||||
resultcxt = CurrentMemoryContext;
|
||||
|
||||
/*
|
||||
* Start a transaction so we can access pg_database, and get a snapshot.
|
||||
* We don't have a use for the snapshot itself, but we're interested in
|
||||
* the secondary effect that it sets RecentGlobalXmin. (This is critical
|
||||
* for anything that reads heap pages, because HOT may decide to prune
|
||||
* them even if the process doesn't attempt to modify any tuples.)
|
||||
*
|
||||
* FIXME: This comment is inaccurate / the code buggy. A snapshot that is
|
||||
* not pushed/active does not reliably prevent HOT pruning (->xmin could
|
||||
* e.g. be cleared when cache invalidations are processed).
|
||||
* Start a transaction so we can access pg_database.
|
||||
*/
|
||||
StartTransactionCommand();
|
||||
(void) GetTransactionSnapshot();
|
||||
|
||||
rel = table_open(DatabaseRelationId, AccessShareLock);
|
||||
scan = table_beginscan_catalog(rel, 0, NULL);
|
||||
|
@ -121,18 +121,9 @@ get_subscription_list(void)
|
||||
resultcxt = CurrentMemoryContext;
|
||||
|
||||
/*
|
||||
* Start a transaction so we can access pg_database, and get a snapshot.
|
||||
* We don't have a use for the snapshot itself, but we're interested in
|
||||
* the secondary effect that it sets RecentGlobalXmin. (This is critical
|
||||
* for anything that reads heap pages, because HOT may decide to prune
|
||||
* them even if the process doesn't attempt to modify any tuples.)
|
||||
*
|
||||
* FIXME: This comment is inaccurate / the code buggy. A snapshot that is
|
||||
* not pushed/active does not reliably prevent HOT pruning (->xmin could
|
||||
* e.g. be cleared when cache invalidations are processed).
|
||||
* Start a transaction so we can access pg_subscription.
|
||||
*/
|
||||
StartTransactionCommand();
|
||||
(void) GetTransactionSnapshot();
|
||||
|
||||
rel = table_open(SubscriptionRelationId, AccessShareLock);
|
||||
scan = table_beginscan_catalog(rel, 0, NULL);
|
||||
|
@ -813,16 +813,7 @@ InitPostgres(const char *in_dbname, Oid dboid,
|
||||
}
|
||||
|
||||
/*
|
||||
* Start a new transaction here before first access to db, and get a
|
||||
* snapshot. We don't have a use for the snapshot itself, but we're
|
||||
* interested in the secondary effect that it sets RecentGlobalXmin. (This
|
||||
* is critical for anything that reads heap pages, because HOT may decide
|
||||
* to prune them even if the process doesn't attempt to modify any
|
||||
* tuples.)
|
||||
*
|
||||
* FIXME: This comment is inaccurate / the code buggy. A snapshot that is
|
||||
* not pushed/active does not reliably prevent HOT pruning (->xmin could
|
||||
* e.g. be cleared when cache invalidations are processed).
|
||||
* Start a new transaction here before first access to db.
|
||||
*/
|
||||
if (!bootstrap)
|
||||
{
|
||||
@ -837,8 +828,6 @@ InitPostgres(const char *in_dbname, Oid dboid,
|
||||
* Fortunately, "read committed" is plenty good enough.
|
||||
*/
|
||||
XactIsoLevel = XACT_READ_COMMITTED;
|
||||
|
||||
(void) GetTransactionSnapshot();
|
||||
}
|
||||
|
||||
/*
|
||||
|
Loading…
x
Reference in New Issue
Block a user