reallocing without oom check in pg_regress

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: reallocing without oom check in pg_regress
Date: 2022-02-23 21:32:30
Message-ID: 9FC7E603-9246-4C62-B466-A39CFAF454AE@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

In pg_regress we realloc() with the destination and source pointer being equal,
without checking for OOM. While a fairly unlikely source of errors, is there a
reason not to use pg_realloc() there for hygiene?

--
Daniel Gustafsson https://vmware.com/

Attachment Content-Type Size
pg_regress_realloc.diff application/octet-stream 406 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-02-23 21:44:44 Re: convert libpq uri-regress tests to tap test
Previous Message Melanie Plageman 2022-02-23 21:30:50 GiST index build missing smgrimmedsync()?