Re: BUG #17053: Memory corruption in parser on prepared query reuse

Charles Samborski <demurgos@demurgos.net>

From: Charles Samborski <demurgos@demurgos.net>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: pgsql-bugs@lists.postgresql.org

Date: 2021-08-19T13:07:35Z

Lists: pgsql-bugs

I am not familiar with how Postgres tracks its bugs. How can I check the
status of this bug #17053? Is it still pending?

> The attached patch seems to fix it.  I wonder though if we ought to
> move the copying to someplace more centralized.  I cannot escape the
> suspicion that there are more of these creepy-crawlies in other
> poorly-tested utility statements.

Is the quick-fix already applied or do you want to wait for these
larger changes? I was hoping to drop my workarounds once the fixes for
this bug land.

Regards,
Charles Samborski

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Avoid scribbling on input node tree in CREATE/ALTER DOMAIN.
- f172438ef6ff 10.18 landed
- b2c740c426da 12.8 landed
- 4b8b3562e1e6 11.13 landed
- 1a3d30255a4e 9.6.23 landed
- 102f31a208b8 13.4 landed
Centralize the logic for protective copying of utility statements.
- 7c337b6b527b 14.0 landed