pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
8+ messages / 5 participants
[nested] [flat]
Commits from this thread:
2026-11-01 180f3dcd41 4fbae91459 6437d97742 c3ef3f2283 e8191e13f6 c6cb792e81 35848657c6 Fix pgoutput crash on missing option values
* BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-24 22:28 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 8+ messages in thread
From: PG Bug reporting form @ 2026-10-24 22:28 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: brar@gmx.de
The following bug has been logged on the website:
Bug reference: 19795
Logged by: Brar Piening
Email address: brar@gmx.de
PostgreSQL version: 18.6
Operating system: Windows 11 x64 (EDB installer builds)
Description:
A START_REPLICATION option without a value crashes the walsender when the
output plugin is pgoutput and the option is proto_version or
publication_names.
The postmaster then restarts all sessions.
A role with REPLICATION is enough; it doesn't need to be a superuser.
Steps, on a fresh cluster with wal_level = logical:
-- as a superuser
CREATE PUBLICATION pub FOR ALL TABLES;
SELECT pg_create_logical_replication_slot('s', 'pgoutput');
CREATE ROLE repuser LOGIN REPLICATION;
pg_recvlogical -d postgres -U repuser --slot=s --start -o proto_version \
-f - --no-loop
(Without --no-loop, pg_recvlogical sends the command again after a few
seconds.)
pg_recvlogical sends START_REPLICATION SLOT "s" LOGICAL 0/0
("proto_version")
and reports:
pg_recvlogical: error: could not send replication command
"START_REPLICATION SLOT "s" LOGICAL 0/0 ("proto_version")": server closed
the connection unexpectedly
Server log (18.6):
LOG: client backend (PID 21132) was terminated by exception 0xC0000005
DETAIL: Failed process was running: START_REPLICATION SLOT "s" LOGICAL
0/0 ("proto_version")
LOG: terminating any other active server processes
LOG: all server processes terminated; reinitializing
LOG: database system was not properly shut down; automatic recovery in
progress
...
LOG: database system is ready to accept connections
"-o publication_names" crashes the same way. I reproduced both on 14.24,
15.19, 16.15, 17.11 and 18.6, all Windows builds, where the crash shows up
as an access violation.
Expected: an error, as for pgoutput's origin option without a value:
ERROR: origin requires a parameter
CONTEXT: slot "s", output plugin "pgoutput", in the startup callback
Cause: the replication grammar accepts an option without a value and leaves
DefElem.arg NULL (repl_gram.y, plugin_opt_arg: "| /* EMPTY */ { $$ = NULL;
}").
parse_output_parameters() in pgoutput.c allows this ("Assert(defel->arg ==
NULL || IsA(defel->arg, String))"), but for proto_version and
publication_names it calls strVal(defel->arg), which dereferences the NULL
pointer.
The other options are read with defGetBoolean() (a missing value means true)
or defGetString() (origin, which raises the error above).
The SQL functions such as pg_logical_slot_get_changes() can't produce a NULL
arg, since logicalfuncs.c wraps every value in makeString().
So only the replication protocol path crashes.
test_decoding checks for a NULL arg itself.
Suggested fix: read both options with defGetString(defel), as origin does,
on all supported branches.
I found this while working on Npgsql (the .NET driver), whose generic
logical replication API currently sends an option without a value when the
caller passes null.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-25 15:31 Zhijie Hou <houzhijie22@gmail.com>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 8+ messages in thread
From: Zhijie Hou @ 2026-10-25 15:31 UTC (permalink / raw)
To: brar@gmx.de; pgsql-bugs@lists.postgresql.org
Hi,
On Sun, Oct 25, 2026 at 9:31 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 19795
> Logged by: Brar Piening
> Email address: brar@gmx.de
> PostgreSQL version: 18.6
> Operating system: Windows 11 x64 (EDB installer builds)
> Description:
>
> A START_REPLICATION option without a value crashes the walsender when the
> output plugin is pgoutput and the option is proto_version or
> publication_names.
> The postmaster then restarts all sessions.
> A role with REPLICATION is enough; it doesn't need to be a superuser.
>
> Steps, on a fresh cluster with wal_level = logical:
>
> -- as a superuser
> CREATE PUBLICATION pub FOR ALL TABLES;
> SELECT pg_create_logical_replication_slot('s', 'pgoutput');
> CREATE ROLE repuser LOGIN REPLICATION;
>
> pg_recvlogical -d postgres -U repuser --slot=s --start -o proto_version \
> -f - --no-loop
>
> (Without --no-loop, pg_recvlogical sends the command again after a few
> seconds.)
>
> pg_recvlogical sends START_REPLICATION SLOT "s" LOGICAL 0/0
> ("proto_version")
> and reports:
>
> pg_recvlogical: error: could not send replication command
> "START_REPLICATION SLOT "s" LOGICAL 0/0 ("proto_version")": server closed
> the connection unexpectedly
>
> Server log (18.6):
>
> LOG: client backend (PID 21132) was terminated by exception 0xC0000005
> DETAIL: Failed process was running: START_REPLICATION SLOT "s" LOGICAL
> 0/0 ("proto_version")
> LOG: terminating any other active server processes
> LOG: all server processes terminated; reinitializing
> LOG: database system was not properly shut down; automatic recovery in
> progress
> ...
> LOG: database system is ready to accept connections
>
> "-o publication_names" crashes the same way. I reproduced both on 14.24,
> 15.19, 16.15, 17.11 and 18.6, all Windows builds, where the crash shows up
> as an access violation.
>
> Expected: an error, as for pgoutput's origin option without a value:
>
> ERROR: origin requires a parameter
> CONTEXT: slot "s", output plugin "pgoutput", in the startup callback
>
> Cause: the replication grammar accepts an option without a value and leaves
> DefElem.arg NULL (repl_gram.y, plugin_opt_arg: "| /* EMPTY */ { $$ = NULL;
> }").
> parse_output_parameters() in pgoutput.c allows this ("Assert(defel->arg ==
> NULL || IsA(defel->arg, String))"), but for proto_version and
> publication_names it calls strVal(defel->arg), which dereferences the NULL
> pointer.
> The other options are read with defGetBoolean() (a missing value means true)
> or defGetString() (origin, which raises the error above).
> The SQL functions such as pg_logical_slot_get_changes() can't produce a NULL
> arg, since logicalfuncs.c wraps every value in makeString().
> So only the replication protocol path crashes.
> test_decoding checks for a NULL arg itself.
>
> Suggested fix: read both options with defGetString(defel), as origin does,
> on all supported branches.
>
> I found this while working on Npgsql (the .NET driver), whose generic
> logical replication API currently sends an option without a value when the
> caller passes null.
Thanks for the report and analysis. I could reproduce the crash, and I
agree with the suggested fix.
Attached is a patch that uses defGetString() for "proto_version" and
"publication_names" and adds a simple test in 030_pg_recvlogical.pl
to confirm it works.
Best Regards,
Zhijie Hou
Attachments:
v1-0001-Fix-pgoutput-crash-on-missing-option-values.patch (application/x-patch, 3.1K) download
From 719b20c7673867b6b5872b8b38fb9946feabfd73 Mon Sep 17 00:00:00 2001
From: Zhijie Hou <houzhijie22@gmail.com>
Date: Sun, 25 Oct 2026 23:19:28 +0800
Subject: [PATCH v1] Fix pgoutput crash on missing option values.
The replication protocol allows options without values, but pgoutput
dereferenced a NULL DefElem argument for proto_version and
publication_names. A replication client could therefore crash the
walsender and force the postmaster to restart all sessions.
Fix this by reading both options with defGetString(), which reports a
missing parameter cleanly.
Reported-by: Brar Piening <brar@gmx.de>
Discussion: https://postgr.es/m/19795-6d7d506133b7f062@postgresql.org
Backpatch-through: 14
---
src/backend/replication/pgoutput/pgoutput.c | 4 +--
src/bin/pg_basebackup/t/030_pg_recvlogical.pl | 35 +++++++++++++++++++
2 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/src/backend/replication/pgoutput/pgoutput.c b/src/backend/replication/pgoutput/pgoutput.c
index b481d5bb388..58a8ae6d45c 100644
--- a/src/backend/replication/pgoutput/pgoutput.c
+++ b/src/backend/replication/pgoutput/pgoutput.c
@@ -316,7 +316,7 @@ parse_output_parameters(List *options, PGOutputData *data)
{
unsigned long parsed;
char *endptr;
- const char *val = strVal(defel->arg);
+ const char *val = defGetString(defel);
if (protocol_version_given)
ereport(ERROR,
@@ -351,7 +351,7 @@ parse_output_parameters(List *options, PGOutputData *data)
* Pass a copy of the DefElem->arg since SplitIdentifierString
* modifies its input.
*/
- if (!SplitIdentifierString(pstrdup(strVal(defel->arg)), ',',
+ if (!SplitIdentifierString(pstrdup(defGetString(defel)), ',',
&data->publication_names))
ereport(ERROR,
(errcode(ERRCODE_INVALID_NAME),
diff --git a/src/bin/pg_basebackup/t/030_pg_recvlogical.pl b/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
index 07ad07fef2a..309a6c04044 100644
--- a/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
+++ b/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
@@ -100,6 +100,41 @@ $node->command_ok(
],
'slot dropped');
+# Check that pgoutput rejects options that require a parameter when passed
+# without a value.
+$node->safe_psql('postgres',
+ "SELECT pg_create_logical_replication_slot('pgoutput_slot', 'pgoutput')");
+
+$node->command_fails_like(
+ [
+ 'pg_recvlogical',
+ '--slot' => 'pgoutput_slot',
+ '--dbname' => $node->connstr('postgres'),
+ '--start',
+ '--option' => 'proto_version',
+ '--no-loop',
+ '--file' => '-',
+ ],
+ qr/proto_version requires a parameter/,
+ 'pgoutput proto_version option without a value');
+
+$node->command_fails_like(
+ [
+ 'pg_recvlogical',
+ '--slot' => 'pgoutput_slot',
+ '--dbname' => $node->connstr('postgres'),
+ '--start',
+ '--option' => 'proto_version=1',
+ '--option' => 'publication_names',
+ '--no-loop',
+ '--file' => '-',
+ ],
+ qr/publication_names requires a parameter/,
+ 'pgoutput publication_names option without a value');
+
+$node->safe_psql('postgres',
+ "SELECT pg_drop_replication_slot('pgoutput_slot')");
+
#test with two-phase option enabled
$node->command_ok(
[
--
2.54.0 (Apple Git-157)
^ permalink raw reply [nested|flat] 8+ messages in thread
* RE: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-26 02:56 Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
parent: Zhijie Hou <houzhijie22@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Hayato Kuroda (Fujitsu) @ 2026-10-26 02:56 UTC (permalink / raw)
To: Zhijie Hou <houzhijie22@gmail.com>; +Cc: brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Hi,
> Attached is a patch that uses defGetString() for "proto_version" and
> "publication_names" and adds a simple test in 030_pg_recvlogical.pl
> to confirm it works.
Thanks for the patch. One question:
```
if (parsed > PG_UINT32_MAX)
ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE),
errmsg("proto_version \"%s\" out of range",
strVal(defel->arg))));
```
Here strVal() is still used, but I feel it's better to refer `val` here. We can completely remove
the function call.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-27 17:36 Kirill Reshke <reshkekirill@gmail.com>
parent: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
1 sibling, 1 reply; 8+ messages in thread
From: Kirill Reshke @ 2026-10-27 17:36 UTC (permalink / raw)
To: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>; +Cc: Zhijie Hou <houzhijie22@gmail.com>; brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
On Mon, 26 Oct 2026 at 07:56, Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>
> Hi,
>
> > Attached is a patch that uses defGetString() for "proto_version" and
> > "publication_names" and adds a simple test in 030_pg_recvlogical.pl
> > to confirm it works.
>
> Thanks for the patch. One question:
>
> ```
> if (parsed > PG_UINT32_MAX)
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> errmsg("proto_version \"%s\" out of range",
> strVal(defel->arg))));
> ```
>
> Here strVal() is still used, but I feel it's better to refer `val` here. We can completely remove
> the function call.
>
> Best regards,
> Hayato Kuroda
> FUJITSU LIMITED
Hi!
Looks like a real issue. I reviewed a patch, I think this is a natural
follow-up for [0]. the CREATE_REPLICATION_SLOT/ALTER_REPLICATION_SLOT
option parser only uses defGetString/defGetBoolean - pgoutput is the
only crasher.
Also, should we reject option like
ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE),
errmsg("option \"%s\" requires a value",
"publication_names")));
instead of a generic error message from defGetString?
[0] https://github.com/postgres/postgres/commit/290bb8afe6b
--
Best regards,
Kirill Reshke
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-31 11:31 Zhijie Hou <houzhijie22@gmail.com>
parent: Kirill Reshke <reshkekirill@gmail.com>
0 siblings, 0 replies; 8+ messages in thread
From: Zhijie Hou @ 2026-10-31 11:31 UTC (permalink / raw)
To: Kirill Reshke <reshkekirill@gmail.com>; Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>; +Cc: brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Hi,
On Wed, Oct 28, 2026 at 01:36 AM Kirill Reshke wrote:
> Looks like a real issue. I reviewed a patch, I think this is a natural
> follow-up for [0]. the CREATE_REPLICATION_SLOT/ALTER_REPLICATION_SLOT
> option parser only uses defGetString/defGetBoolean - pgoutput is the
> only crasher.
>
> Also, should we reject option like
>
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> errmsg("option \"%s\" requires a value",
> "publication_names")));
>
>
> instead of a generic error message from defGetString?
I think a special message is unnecessary here, especially since we don't
do that in other replication parsing code, so I've kept the current version.
--
Best Regards,
Zhijie Hou
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-10-31 11:32 Zhijie Hou <houzhijie22@gmail.com>
parent: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
1 sibling, 1 reply; 8+ messages in thread
From: Zhijie Hou @ 2026-10-31 11:32 UTC (permalink / raw)
To: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>; +Cc: brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Hi,
On Mon, Oct 26, 2026 at 10:56 AM "Hayato Kuroda (Fujitsu)" wrote:
>
>> Attached is a patch that uses defGetString() for "proto_version" and
>> "publication_names" and adds a simple test in 030_pg_recvlogical.pl
>> to confirm it works.
>
> Thanks for the patch. One question:
>
> ```
> if (parsed > PG_UINT32_MAX)
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_PARAMETER_VALUE),
> errmsg("proto_version \"%s\" out of range",
> strVal(defel->arg))));
> ```
>
> Here strVal() is still used, but I feel it's better to refer `val` here. We can completely remove
> the function call.
Thanks for reviewing.
Here is the V2 patch.
--
Best Regards,
Zhijie Hou
Attachments:
v2-0001-Fix-pgoutput-crash-on-missing-option-values.patch (text/plain, 3.6K) download
From 54068fa3084f7279ce28b1e9c843f716a65a7bb6 Mon Sep 17 00:00:00 2001
From: Zhijie Hou <houzhijie22@gmail.com>
Date: Fri, 30 Oct 2026 12:29:51 +0800
Subject: [PATCH v2] Fix pgoutput crash on missing option values.
The replication protocol allows options without values, but pgoutput
dereferenced a NULL DefElem argument for proto_version and
publication_names. A replication client could therefore crash the
walsender and force the postmaster to restart all sessions.
Fix this by reading both options with defGetString(), which reports a
missing parameter cleanly.
Reported-by: Brar Piening <brar@gmx.de>
Author: Zhijie Hou <houzhijie22@gmail.com>
Reviewed-by: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Reviewed-by: Kirill Reshke <reshkekirill@gmail.com>
Discussion: https://postgr.es/m/19795-6d7d506133b7f062@postgresql.org
Backpatch-through: 14
---
src/backend/replication/pgoutput/pgoutput.c | 7 ++--
src/bin/pg_basebackup/t/030_pg_recvlogical.pl | 35 +++++++++++++++++++
2 files changed, 38 insertions(+), 4 deletions(-)
diff --git a/src/backend/replication/pgoutput/pgoutput.c b/src/backend/replication/pgoutput/pgoutput.c
index b481d5bb388..c8caa163c15 100644
--- a/src/backend/replication/pgoutput/pgoutput.c
+++ b/src/backend/replication/pgoutput/pgoutput.c
@@ -316,7 +316,7 @@ parse_output_parameters(List *options, PGOutputData *data)
{
unsigned long parsed;
char *endptr;
- const char *val = strVal(defel->arg);
+ const char *val = defGetString(defel);
if (protocol_version_given)
ereport(ERROR,
@@ -334,8 +334,7 @@ parse_output_parameters(List *options, PGOutputData *data)
if (parsed > PG_UINT32_MAX)
ereport(ERROR,
(errcode(ERRCODE_INVALID_PARAMETER_VALUE),
- errmsg("proto_version \"%s\" out of range",
- strVal(defel->arg))));
+ errmsg("proto_version \"%s\" out of range", val)));
data->protocol_version = (uint32) parsed;
}
@@ -351,7 +350,7 @@ parse_output_parameters(List *options, PGOutputData *data)
* Pass a copy of the DefElem->arg since SplitIdentifierString
* modifies its input.
*/
- if (!SplitIdentifierString(pstrdup(strVal(defel->arg)), ',',
+ if (!SplitIdentifierString(pstrdup(defGetString(defel)), ',',
&data->publication_names))
ereport(ERROR,
(errcode(ERRCODE_INVALID_NAME),
diff --git a/src/bin/pg_basebackup/t/030_pg_recvlogical.pl b/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
index 07ad07fef2a..309a6c04044 100644
--- a/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
+++ b/src/bin/pg_basebackup/t/030_pg_recvlogical.pl
@@ -100,6 +100,41 @@ $node->command_ok(
],
'slot dropped');
+# Check that pgoutput rejects options that require a parameter when passed
+# without a value.
+$node->safe_psql('postgres',
+ "SELECT pg_create_logical_replication_slot('pgoutput_slot', 'pgoutput')");
+
+$node->command_fails_like(
+ [
+ 'pg_recvlogical',
+ '--slot' => 'pgoutput_slot',
+ '--dbname' => $node->connstr('postgres'),
+ '--start',
+ '--option' => 'proto_version',
+ '--no-loop',
+ '--file' => '-',
+ ],
+ qr/proto_version requires a parameter/,
+ 'pgoutput proto_version option without a value');
+
+$node->command_fails_like(
+ [
+ 'pg_recvlogical',
+ '--slot' => 'pgoutput_slot',
+ '--dbname' => $node->connstr('postgres'),
+ '--start',
+ '--option' => 'proto_version=1',
+ '--option' => 'publication_names',
+ '--no-loop',
+ '--file' => '-',
+ ],
+ qr/publication_names requires a parameter/,
+ 'pgoutput publication_names option without a value');
+
+$node->safe_psql('postgres',
+ "SELECT pg_drop_replication_slot('pgoutput_slot')");
+
#test with two-phase option enabled
$node->command_ok(
[
--
2.54.0 (Apple Git-157)
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-11-01 08:00 Michael Paquier <michael@paquier.xyz>
parent: Zhijie Hou <houzhijie22@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Michael Paquier @ 2026-11-01 08:00 UTC (permalink / raw)
To: Zhijie Hou <houzhijie22@gmail.com>; +Cc: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>; brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
On Sat, Oct 31, 2026 at 07:32:00PM +0800, Zhijie Hou wrote:
> Thanks for reviewing.
>
> Here is the V2 patch.
Thanks for the patch, nice catch. I'll handle that and backpatch.
I regret missing that during the lookup of this code for 290bb8afe6b4,
especially as the crash was possible before it for the two code paths
you are pointing at with the two direct accesses to defel->arg.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value
@ 2026-11-01 23:15 Michael Paquier <michael@paquier.xyz>
parent: Michael Paquier <michael@paquier.xyz>
0 siblings, 0 replies; 8+ messages in thread
From: Michael Paquier @ 2026-11-01 23:15 UTC (permalink / raw)
To: Zhijie Hou <houzhijie22@gmail.com>; +Cc: Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>; brar@gmx.de <brar@gmx.de>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
On Sun, Nov 01, 2026 at 05:00:31PM +0900, Michael Paquier wrote:
> Thanks for the patch, nice catch. I'll handle that and backpatch.
> I regret missing that during the lookup of this code for 290bb8afe6b4,
> especially as the crash was possible before it for the two code paths
> you are pointing at with the two direct accesses to defel->arg.
Applied down to v14 as of 35848657c67d. Thanks, all.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2026-11-01 23:15 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-10-24 22:28 BUG #19795: pgoutput: walsender crashes on START_REPLICATION option without a value PG Bug reporting form <noreply@postgresql.org>
2026-10-25 15:31 ` Zhijie Hou <houzhijie22@gmail.com>
2026-10-26 02:56 ` Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
2026-10-27 17:36 ` Kirill Reshke <reshkekirill@gmail.com>
2026-10-31 11:31 ` Zhijie Hou <houzhijie22@gmail.com>
2026-10-31 11:32 ` Zhijie Hou <houzhijie22@gmail.com>
2026-11-01 08:00 ` Michael Paquier <michael@paquier.xyz>
2026-11-01 23:15 ` Michael Paquier <michael@paquier.xyz>
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