mirror of
https://github.com/postgres/postgres.git
synced 2025-07-15 19:21:59 +03:00
Replace max_expr_depth parameter with a max_stack_depth parameter that
is measured in kilobytes and checked against actual physical execution stack depth, as per my proposal of 30-Dec. This gives us a fairly bulletproof defense against crashing due to runaway recursive functions.
This commit is contained in:
@ -3,7 +3,7 @@
|
||||
*
|
||||
* Copyright (c) 2000-2003, PostgreSQL Global Development Group
|
||||
*
|
||||
* $PostgreSQL: pgsql/src/bin/psql/tab-complete.c,v 1.102 2004/03/23 01:23:48 tgl Exp $
|
||||
* $PostgreSQL: pgsql/src/bin/psql/tab-complete.c,v 1.103 2004/03/24 22:40:29 tgl Exp $
|
||||
*/
|
||||
|
||||
/*----------------------------------------------------------------------
|
||||
@ -535,11 +535,11 @@ psql_completion(char *text, int start, int end)
|
||||
"log_statement_stats",
|
||||
"maintenance_work_mem",
|
||||
"max_connections",
|
||||
"max_expr_depth",
|
||||
"max_files_per_process",
|
||||
"max_fsm_pages",
|
||||
"max_fsm_relations",
|
||||
"max_locks_per_transaction",
|
||||
"max_stack_depth",
|
||||
"password_encryption",
|
||||
"port",
|
||||
"random_page_cost",
|
||||
|
Reference in New Issue
Block a user