From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | bogus assert in logicalmsg_desc |
Date: | 2022-08-14 16:16:53 |
Message-ID: | b99b6101-2f14-3796-3dfa-4a6cd7d4326d@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
while experimenting with logical messages, I ran into this assert in
logicalmsg_desc:
Assert(prefix[xlrec->prefix_size] != '\0');
This seems to be incorrect, because LogLogicalMessage does this:
xlrec.prefix_size = strlen(prefix) + 1;
So prefix_size includes the null byte, so the assert points out at the
first payload byte. And of course, the check should be "==" because we
expect the byte to be \0, not the other way around.
It's pretty simple to make this crash by writing a logical message where
the first payload byte is \0, e.g. like this:
select pg_logical_emit_message(true, 'a'::text, '\x00'::bytea);
and then running pg_waldump on the WAL segment.
Attached is a patch addressing this. This was added in 14, so we should
backpatch to that version.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
logicalmsgdesc-fix.patch | text/x-patch | 642 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2022-08-14 16:54:42 | Re: Include the dependent extension information in describe command. |
Previous Message | vignesh C | 2022-08-14 14:26:00 | Re: Tab completion for "ALTER TYPE typename SET" and rearranged "Alter TYPE typename RENAME" |