From 48938ab50686b98d2af4536bbf342a5011393815 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 26 May 2009 17:36:05 +0000 Subject: Allow the second argument of pg_get_expr() to be just zero when deparsing an expression that's not supposed to contain variables. Per discussion with Gevik Babakhani, this eliminates the need for an ugly kluge (namely, specifying some unrelated relation name). Remove one such kluge from pg_dump. --- doc/src/sgml/func.sgml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index faf0e30b157..a594a12ed7b 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,4 +1,4 @@ - + Functions and Operators @@ -12367,7 +12367,9 @@ SELECT pg_type_is_visible('myschema.widget'::regtype); is a decompiled reconstruction, not the original text of the command.) pg_get_expr decompiles the internal form of an individual expression, such as the default value for a column. It can be - useful when examining the contents of system catalogs. + useful when examining the contents of system catalogs. If the expression + might contain Vars, specify the OID of the relation they refer to as the + second parameter; if no Vars are expected, zero is sufficient. pg_get_viewdef reconstructs the SELECT query that defines a view. Most of these functions come in two variants, one of which can optionally pretty-print the result. The -- cgit v1.2.3