database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-10 17:42:29 +03:00
Code Activity

Out-of-bounds memory allocation request sizes should be treated as just

Browse Source 
elog(ERROR) not an Assert trap, since we've downgraded out-of-memory to
elog(ERROR) not a fatal error.  Also, change the hard boundary from 256Mb
to 1Gb, just so that anyone who's actually got that much memory to spare
can play with TOAST objects approaching a gigabyte.
This commit is contained in:
Tom Lane
2001-02-06 01:53:53 +00:00
parent 192ce19d36
commit 85c17dbff8
4 changed files with 14 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/backend/utils/error/excid.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/excid.c,v 1.9 2001/01/24 19:43:15 momjian Exp $
* $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/excid.c,v 1.10 2001/02/06 01:53:53 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -42,18 +42,6 @@ Exception BadArg = {"Bad Argument to Function Call"};
* Specific Recoverable Exceptions *
*****************************************************************************/
/*
* BadAllocSize
* Indicates that an allocation request is of unreasonable size.
*/
Exception BadAllocSize = {"Too Large Allocation Request"};
/*
* ExhaustedMemory
* Indicates an dynamic memory allocation failed.
*/
Exception ExhaustedMemory = {"Memory Allocation Failed"};
/*
* Unimplemented
* Indicates a function call request requires unimplemented code.