v0-0001-Fix-incorrect-function-reference-in-comment.patch
application/octet-stream
Filename: v0-0001-Fix-incorrect-function-reference-in-comment.patch
Type: application/octet-stream
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v0-0001
Subject: Fix incorrect function reference in comment.
| File | + | − |
|---|---|---|
| src/backend/utils/sort/logtape.c | 1 | 1 |
From 95af858d2a9bc2365add7e5ee2afbd6ec2f7a881 Mon Sep 17 00:00:00 2001
From: Zhang Mingli <avamingli@gmail.com>
Date: Wed, 1 Oct 2025 16:09:59 +0800
Subject: [PATCH] Fix incorrect function reference in comment.
The comment incorrectly cited the defunct function BufFileOpenShared()
which is replaced in commit dcac5e7ac157964f71f15d81c7429130c69c3f9b.
Update the reference to the current function: BufFileOpenFileSet().
Authored-by: Zhang Mingli avamingli@gmail.com
---
src/backend/utils/sort/logtape.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/backend/utils/sort/logtape.c b/src/backend/utils/sort/logtape.c
index e529ceb826..452d89a8c0 100644
--- a/src/backend/utils/sort/logtape.c
+++ b/src/backend/utils/sort/logtape.c
@@ -681,7 +681,7 @@ LogicalTapeCreate(LogicalTapeSet *lts)
{
/*
* The only thing that currently prevents creating new tapes in leader is
- * the fact that BufFiles opened using BufFileOpenShared() are read-only
+ * the fact that BufFiles opened using BufFileOpenFileSet() are read-only
* by definition, but that could be changed if it seemed worthwhile. For
* now, writing to the leader tape will raise a "Bad file descriptor"
* error, so tuplesort must avoid writing to the leader tape altogether.
--
2.34.1