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

Commit7c298c6

Browse files
committed
Add comment about extract_autovac_opts not holding lock
Per observation from Tom Lane.Discussion:https://postgr.es/m/1901125.1617904665@sss.pgh.pa.us
1 parent7b357cc commit7c298c6

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

‎src/backend/postmaster/autovacuum.c

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2783,6 +2783,11 @@ perform_work_item(AutoVacuumWorkItem *workitem)
27832783
*
27842784
* Given a relation's pg_class tuple, return the AutoVacOpts portion of
27852785
* reloptions, if set; otherwise, return NULL.
2786+
*
2787+
* Note: callers do not have a relation lock on the table at this point,
2788+
* so the table could have been dropped, and its catalog rows gone, after
2789+
* we acquired the pg_class row. If pg_class had a TOAST table, this would
2790+
* be a risk; fortunately, it doesn't.
27862791
*/
27872792
staticAutoVacOpts*
27882793
extract_autovac_opts(HeapTupletup,TupleDescpg_class_desc)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp