Re: Avoid possible dereference null pointer (src/backend/catalog/pg_depend.c)
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Ranier Vilela <ranier.vf@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-24T11:48:32Z
Lists: pgsql-hackers
Attachments
- 0001-Fix-potential-NULL-pointer-dereference-in-g-20240524.patch (text/x-patch) patch 0001
On Fri, May 24, 2024 at 12:16 PM Michael Paquier <michael@paquier.xyz> wrote: > On Fri, May 24, 2024 at 11:58:51AM +0530, Ashutosh Bapat wrote: > > If we are looking for avoiding a segfault and get a message which helps > > debugging, using get_attname and get_attnum might be better options. > > get_attname throws an error. get_attnum doesn't throw an error and > returns > > InvalidAttnum which won't return any valid identity sequence, and thus > > return a NIL sequence list which is handled in that function already. > Using > > these two functions will avoid the clutter as well as segfault. If that's > > acceptable, I will provide a patch. > > Yeah, you could do that with these two routines as well. The result > would be the same in terms of runtime validity checks. > PFA patch using those two routines. -- Best Wishes, Ashutosh Bapat
Commits
-
Fix potential NULL pointer dereference in getIdentitySequence()
- 8285b484a47d 17.0 landed
-
Fix assorted bugs related to identity column in partitioned tables
- 509199587df7 17.0 cited