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

Commit864db11

Browse files
committed
Update obsolete comment.
We no longer use GetNewOidWithIndex on pg_largeobject; rather,pg_largeobject_metadata's regular OID column is considered the repositoryof OIDs for large objects. The special functionality is still needed forTOAST tables however.
1 parent8255566 commit864db11

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

‎src/backend/catalog/catalog.c

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -472,10 +472,10 @@ GetNewOid(Relation relation)
472472
*
473473
* This is exported separately because there are cases where we want to use
474474
* an index that will not be recognized by RelationGetOidIndex: TOAST tables
475-
*and pg_largeobjecthave indexes that are usable, but have multiple columns
476-
*and are onordinary columns rather than a true OID column. This code
477-
*will workanyway, so long as the OID is the index's first column. The
478-
*caller mustpass in the actual heap attnum of the OID column, however.
475+
* have indexes that are usable, but have multiple columns and are on
476+
* ordinary columns rather than a true OID column. This code will work
477+
* anyway, so long as the OID is the index's first column. The caller must
478+
* pass in the actual heap attnum of the OID column, however.
479479
*
480480
* Caller must have a suitable lock on the relation.
481481
*/

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp