Re: Assert name/short_desc to prevent SHOW ALL segfault
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Steve Chavez <steve@supabase.io>, pgsql-hackers@postgresql.org
Date: 2022-05-26T21:45:50Z
Lists: pgsql-hackers
Attachments
On Tue, May 24, 2022 at 11:17:39PM -0700, Andres Freund wrote: > On 2022-05-24 11:41:49 -0700, Nathan Bossart wrote: >> I would actually ERROR on this so that we aren't relying on >> --enable-cassert builds to catch it. > > How about adding pg_nonnull(...) (ending up as __attribute__((nonnull(...))? > Then code passing NULLs would get compiler warnings? It'd be useful in quite a > few more places. I attached an attempt at this for the "name" and "valueAddr" arguments for the DefineCustomXXXVariable functions. It looked like nonnull was supported by GCC and Clang, but I haven't looked too closely to see whether we need version checks as well. >> That being said, if there's no strong reason to enforce that a short >> description be provided, then why not adjust ShowAllGUCConfig() to set that >> column to NULL when short_desc is missing? > > There's a bunch more places that'd need to be adjusted, if we go that way. I > don't really have an opinion on it. I looked around and didn't see anywhere else obvious that needed adjustment besides what Michael pointed out (3ac7d024). Am I missing something? -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Introduce pg_attribute_nonnull(...)
- 0507977aa4a3 16.0 landed
-
Handle NULL for short descriptions of custom GUC variables
- 1b40ceea24e6 10.22 landed
- c3db8a2e2ea4 11.17 landed
- ae236bf660f5 12.12 landed
- 1e6802990cdd 13.8 landed
- fe441a031940 14.4 landed
- f1431f3bffa0 15.0 landed