postgres.git / summary / log / commit / refs

commit    441bbd298888fe751a01b6c74cc53f2e7b223fa9
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Sep 26 21:07:14 2023 +0000
First released in: 17.0

    doc:  correct reference to pg_relation in comment
    
    Reported-by: Dagfinn Ilmari Mannsåker
    
    Discussion: https://postgr.es/m/87sf9apnr0.fsf@wibble.ilmari.org
    
    Backpatch-through: master


 src/backend/storage/large_object/inv_api.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/backend/storage/large_object/inv_api.c b/src/backend/storage/large_object/inv_api.c
index 84e543e7310..cc9c335a92d 100644
--- a/src/backend/storage/large_object/inv_api.c
+++ b/src/backend/storage/large_object/inv_api.c
@@ -58,11 +58,11 @@
 bool		lo_compat_privileges;
 
 /*
- * All accesses to pg_largeobject and its index make use of a single Relation
- * reference, so that we only need to open pg_relation once per transaction.
- * To avoid problems when the first such reference occurs inside a
- * subtransaction, we execute a slightly klugy maneuver to assign ownership of
- * the Relation reference to TopTransactionResourceOwner.
+ * All accesses to pg_largeobject and its index make use of a single
+ * Relation reference.  To guarantee that the relcache entry remains
+ * in the cache, on the first reference inside a subtransaction, we
+ * execute a slightly klugy maneuver to assign ownership of the
+ * Relation reference to TopTransactionResourceOwner.
  */
 static Relation lo_heap_r = NULL;
 static Relation lo_index_r = NULL;


[parent: b0ae29512c21]