Tom Lane 303696c3b4 Install a data-type-based solution for protecting pg_get_expr(). ... Since the code underlying pg_get_expr() is not secure against malformed input, and can't practically be made so, we need to prevent miscreants from feeding arbitrary data to it. We can do this securely by declaring pg_get_expr() to take a new datatype "pg_node_tree" and declaring the system catalog columns that hold nodeToString output to be of that type. There is no way at SQL level to create a non-null value of type pg_node_tree. Since the backend-internal operations that fill those catalog columns operate below the SQL level, they are oblivious to the datatype relabeling and don't need any changes.		2010-09-03 01:34:55 +00:00
..
examples	pgindent run for 9.0, second run	2010-07-06 19:19:02 +00:00
locale	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list	2009-06-11 14:49:15 +00:00
mb	Use diff's -w switch only on Windows, to avoid problems with inconsistent	2009-11-23 16:02:24 +00:00
performance	Remove extra newlines at end and beginning of files, add missing newlines	2010-08-19 05:57:36 +00:00
regress	Install a data-type-based solution for protecting pg_get_expr().	2010-09-03 01:34:55 +00:00
thread	Remove extra newlines at end and beginning of files, add missing newlines	2010-08-19 05:57:36 +00:00
Makefile	$Header: -> $PostgreSQL Changes ...	2003-11-29 19:52:15 +00:00