Avoid possibly accessing off the end of memory in examine_attribute().
Since the last couple of columns of pg_type are often NULL,
sizeof(FormData_pg_type) can be an overestimate of the actual size of the
tuple data part. Therefore memcpy'ing that much out of the catalog cache,
as analyze.c was doing, poses a small risk of copying past the end of
memory and incurring SIGSEGV. No such crash has been identified in the
field, but we've certainly seen the equivalent happen in other code paths,
so patch this one all the way back.
Per valgrind testing by Noah Misch, though this is not his proposed patch.
I chose to use SearchSysCacheCopy1 rather than inventing special-purpose
infrastructure for copying only the minimal part of a pg_type tuple.
src/backend/commands/analyze.c | 12 +++++-------
1 files changed, 5 insertions(+), 7 deletions(-)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2011-09-06 18:53:29|
|Subject: pgsql: Avoid possibly accessing off the end of memory in SJIS2004conve|
|Previous:||From: Bruce Momjian||Date: 2011-09-06 17:42:13|
|Subject: pgsql: Document PERFORM limitation when using WITH queries.|