RE:BUG #18533: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup

From: 1165125080 <1165125080(at)qq(dot)com>
To: 1165125080 <1165125080(at)qq(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE:BUG #18533: pg_basebackup uses out-of-bounds memory and a segment error occurs during backup
Date: 2024-07-17 14:55:58
Message-ID: tencent_D050F6EC2C1B44D0EA302D7C8447526DF208@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

&gt; Do I think we should remove the bbstreamer_buffer_until call in the
&gt; bbstreamer_tar_parser_content function in the scenario of
&gt; BBFLOWER_MEMBER_TRAILER?

It might be more semantically appropriate to change the data in the bbstreamer_content function call to streamer-&gt;bbs_buffer

case BBSTREAMER_MEMBER_TRAILER:
if (!bbstreamer_buffer_until(streamer, &amp;data, &amp;len,
mystreamer-&gt;pad_bytes_expected))
return;

/* OK, now we can send it. */
bbstreamer_content(mystreamer-&gt;base.bbs_next,
&nbsp; &nbsp;&amp;mystreamer-&gt;member,
&nbsp; &nbsp;data, mystreamer-&gt;pad_bytes_expected,
&nbsp; &nbsp;BBSTREAMER_MEMBER_TRAILER);

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-07-17 17:03:25 Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present
Previous Message Aleksander Alekseev 2024-07-17 13:58:26 Re: libpq: unexpected return code from PQexecParams with a DO INSTEAD rule present