Michael Paquier wrote > Attached is a patch adding the following set of functions for frontend > and backends returning NULL instead of reporting ERROR when allocation > fails: > - palloc_safe > - palloc0_safe > - repalloc_safe
The only thing I can contribute is paint...I'm not fond of the word "_safe" and think "_try" would be more informative...in the spirit of try/catch as a means of error handling/recovery. David J. -- View this message in context: http://postgresql.nabble.com/Safe-memory-allocation-functions-tp5833709p5833711.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
