Use SearchSysCacheTupleCopy() instead of SearchSysCacheTuple() in

order to continue to access the tuple more than now.
This would resolve a segmentation fault error.
This commit is contained in:
Hiroshi Inoue 2000-11-10 09:38:21 +00:00
parent 92875e6f44
commit 27026fef60

View File

@ -15,7 +15,7 @@
* *
* *
* IDENTIFICATION * IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/adt/selfuncs.c,v 1.80 2000/10/05 19:48:28 momjian Exp $ * $Header: /cvsroot/pgsql/src/backend/utils/adt/selfuncs.c,v 1.81 2000/11/10 09:38:21 inoue Exp $
* *
*------------------------------------------------------------------------- *-------------------------------------------------------------------------
*/ */
@ -1250,7 +1250,7 @@ getattstatistics(Oid relid,
* have at hand! (For example, we might have a '>' operator rather * have at hand! (For example, we might have a '>' operator rather
* than the '<' operator that will appear in staop.) * than the '<' operator that will appear in staop.)
*/ */
tuple = SearchSysCacheTuple(STATRELID, tuple = SearchSysCacheTupleCopy(STATRELID,
ObjectIdGetDatum(relid), ObjectIdGetDatum(relid),
Int16GetDatum((int16) attnum), Int16GetDatum((int16) attnum),
0, 0,
@ -1351,6 +1351,7 @@ getattstatistics(Oid relid,
pfree(strval); pfree(strval);
} }
} }
heap_freetuple(tuple);
return true; return true;
} }