From: Manu <manuelreyesbravo@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Assertion failure with temporary relations in single-user mode
Date: Mon, 16 Nov 2026 21:32:20 -0300
Message-ID: <179487554022.104798.7544124224648387746@gmail.com> (raw)
Hi,
With assertions enabled, single-user mode fails an assertion as soon
as a temporary relation is read or written through local buffers,
from v16 to master:
$ echo "CREATE TEMP TABLE t AS SELECT 1;" | postgres --single postgres
TRAP: failed Assert("pgstat_tracks_io_op(MyBackendType, ...)")
28e626bde00 put B_STANDALONE_BACKEND in no_temp_rel, in
pgstat_tracks_io_object(), but a single-user backend uses local
buffers like a client backend. Without assertions, that IO is not
counted: pg_stat_io has no "temp relation" row for it.
Patch with a test attached; the test also fails without assertions.
The back branches need small adjustments; tested on 16 to 19.
Regards,
Manu
Attachments:v1-0001-Fix-IO-tracking-of-temporary-relations-in-single-.patch (text/x-patch, 6.5K) download
From ba7dee43c85f62517d59128ee6be788f1fd86fa8 Mon Sep 17 00:00:00 2001
From: Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
Date: Mon, 16 Nov 2026 21:16:54 -0300
Subject: [PATCH v1] Fix IO tracking of temporary relations in single-user mode
pgstat_tracks_io_object() lists B_STANDALONE_BACKEND among the backend
types that never do IO on temporary relations, since 28e626bde00 (v16).
A backend in single-user mode executes queries like a client backend,
and can create and use temporary tables and sequences. With assertions
enabled, an INSERT into a temporary table, CREATE TEMP TABLE AS or
nextval() on a temporary sequence fails the assertion in
pgstat_count_io_op():
$ echo "CREATE TEMP TABLE t AS SELECT 1;" | postgres --single postgres
TRAP: failed Assert("pgstat_tracks_io_op(MyBackendType, io_object, io_context, io_op)")
Without assertions, this IO is not counted: pg_stat_io has no
"temp relation" row for "standalone backend".
Remove B_STANDALONE_BACKEND from this list, and fix the comment above
it. A TAP test runs these commands in single-user mode, with a
temporary table larger than temp_buffers so as local buffers are
evicted, written and read back, then checks pg_stat_io once the server
is started.
Discussion:
---
src/backend/utils/activity/pgstat_io.c | 14 ++--
src/test/modules/test_misc/meson.build | 1 +
.../test_misc/t/016_single_user_temp_io.pl | 79 +++++++++++++++++++
src/test/regress/expected/stats.out | 3 +-
4 files changed, 89 insertions(+), 8 deletions(-)
create mode 100644 src/test/modules/test_misc/t/016_single_user_temp_io.pl
diff --git a/src/backend/utils/activity/pgstat_io.c b/src/backend/utils/activity/pgstat_io.cindex 3c8fcb20..cec57596 100644--- a/src/backend/utils/activity/pgstat_io.c+++ b/src/backend/utils/activity/pgstat_io.c@@ -413,16 +413,16 @@ pgstat_tracks_io_object(BackendType bktype, IOObject io_object,
return false;
/*
- * In core Postgres, only regular backends and WAL Sender processes- * executing queries will use local buffers and operate on temporary- * relations. Parallel workers will not use local buffers (see- * InitLocalBuffers()); however, extensions leveraging background workers- * have no such limitation, so track IO on IOOBJECT_TEMP_RELATION for- * BackendType B_BG_WORKER.+ * In core Postgres, only regular backends, WAL Sender processes executing+ * queries and standalone backends (single-user mode) will use local+ * buffers and operate on temporary relations. Parallel workers will not+ * use local buffers (see InitLocalBuffers()); however, extensions+ * leveraging background workers have no such limitation, so track IO on+ * IOOBJECT_TEMP_RELATION for BackendType B_BG_WORKER.
*/
no_temp_rel = bktype == B_AUTOVAC_LAUNCHER || bktype == B_BG_WRITER ||
bktype == B_CHECKPOINTER || bktype == B_AUTOVAC_WORKER ||
- bktype == B_STANDALONE_BACKEND || bktype == B_STARTUP ||+ bktype == B_STARTUP ||
bktype == B_WAL_SUMMARIZER || bktype == B_WAL_WRITER ||
bktype == B_WAL_RECEIVER;
diff --git a/src/test/modules/test_misc/meson.build b/src/test/modules/test_misc/meson.buildindex 5d81f5b1..f1750847 100644--- a/src/test/modules/test_misc/meson.build+++ b/src/test/modules/test_misc/meson.build@@ -24,6 +24,7 @@ tests += {
't/013_temp_obj_multisession.pl',
't/014_log_statement_max_length.pl',
't/015_temp_schema_exit_deferrable.pl',
+ 't/016_single_user_temp_io.pl',
],
# The injection points are cluster-wide, so disable installcheck
'runningcheck': false,
diff --git a/src/test/modules/test_misc/t/016_single_user_temp_io.pl b/src/test/modules/test_misc/t/016_single_user_temp_io.plnew file mode 100644index 00000000..cc9a7386--- /dev/null+++ b/src/test/modules/test_misc/t/016_single_user_temp_io.pl@@ -0,0 +1,79 @@+# Copyright (c) 2026, PostgreSQL Global Development Group++# Check that a backend in single-user mode can do IO on temporary relations,+# and that this IO is reported in pg_stat_io.++use strict;+use warnings FATAL => 'all';+use PostgreSQL::Test::Cluster;+use PostgreSQL::Test::Utils;+use Test::More;++# Skip the tests on Windows, as single-user mode would fail on permission+# failure with privileged accounts.+if ($windows_os)+{+ plan skip_all => 'this test is not supported by this platform';+}++# Run set of queries in single-user mode.+sub test_single_mode+{+ my ($node, $queries, $testname) = @_;++ my $result = run_log(+ [+ 'postgres', '--single', '-F',+ '-c' => 'exit_on_error=true',+ '-D' => $node->data_dir,+ 'postgres'+ ],+ '<' => \$queries);++ ok($result, $testname);+}++my $node = PostgreSQL::Test::Cluster->new('node');+$node->init;++test_single_mode(+ $node, qq(+CREATE TEMP TABLE temp_insert (a int);+INSERT INTO temp_insert VALUES (1);+),+ "INSERT into temporary table");+test_single_mode(+ $node,+ "CREATE TEMP TABLE temp_ctas AS SELECT 1 AS a;",+ "CREATE TEMP TABLE AS");+test_single_mode(+ $node, qq(+CREATE TEMP SEQUENCE temp_seq;+SELECT nextval('temp_seq');+),+ "nextval() on temporary sequence");++# A temporary table larger than temp_buffers, so as local buffers are+# evicted, written and read back.+test_single_mode(+ $node, qq(+SET temp_buffers = 100;+CREATE TEMP TABLE temp_big AS SELECT g AS a, repeat('x', 100) AS b FROM generate_series(1, 20000) g;+SELECT count(*) FROM temp_big;+),+ "temporary table larger than temp_buffers");++# The IO done on temporary relations by the standalone backend is visible+# once the server is started.+$node->start;+my $result = $node->safe_psql(+ 'postgres', qq(+SELECT extends > 0, reads > 0, writes > 0, evictions > 0, hits > 0+ FROM pg_stat_io+ WHERE backend_type = 'standalone backend' AND+ object = 'temp relation' AND context = 'normal'));+is($result, 't|t|t|t|t',+ "IO on temporary relations of standalone backend in pg_stat_io");+$node->stop;++done_testing();diff --git a/src/test/regress/expected/stats.out b/src/test/regress/expected/stats.outindex 8b154712..b1935882 100644--- a/src/test/regress/expected/stats.out+++ b/src/test/regress/expected/stats.out@@ -81,6 +81,7 @@ standalone backend|relation|bulkwrite
standalone backend|relation|init
standalone backend|relation|normal
standalone backend|relation|vacuum
+standalone backend|temp relation|normal
standalone backend|wal|init
standalone backend|wal|normal
startup|relation|bulkread
@@ -104,7 +105,7 @@ walsummarizer|wal|init
walsummarizer|wal|normal
walwriter|wal|init
walwriter|wal|normal
-(88 rows)+(89 rows)
\a
-- List of registered statistics kinds.
SELECT id, name, fixed_amount,
--
2.56.1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: manuelreyesbravo@gmail.com, michael@paquier.xyz, melanieplageman@gmail.com
Subject: Re: Assertion failure with temporary relations in single-user mode
In-Reply-To: <179487554022.104798.7544124224648387746@gmail.com>
References: <179487554022.104798.7544124224648387746@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox