From eb3adab5685ce5a60bcf96628244f1e2a8e0ab3b Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 21 Sep 2002 18:39:26 +0000 Subject: Provide an upgrade strategy for dump files containing functions declared with OPAQUE. CREATE LANGUAGE, CREATE TRIGGER, and CREATE TYPE will all accept references to functions declared with OPAQUE --- but they will issue a NOTICE, and will modify the function entries in pg_proc to have the preferred type-safe argument or result types instead of OPAQUE. Per recent pghackers discussions. --- doc/src/sgml/ref/create_trigger.sgml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'doc/src/sgml/ref/create_trigger.sgml') diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml index c736dd95df..1134cd800e 100644 --- a/doc/src/sgml/ref/create_trigger.sgml +++ b/doc/src/sgml/ref/create_trigger.sgml @@ -1,5 +1,5 @@ @@ -170,9 +170,10 @@ CREATE TRIGGER In PostgreSQL versions before 7.3, it was necessary to declare trigger functions as returning the placeholder - type opaque, rather than trigger. This is still - supported, but is deprecated because it is obscure and causes loss of - type safety. + type opaque, rather than trigger. To support loading + of old dump files, CREATE TRIGGER will accept a function + declared as returning opaque, but it will issue a NOTICE and + change the function's declared return type to trigger. -- cgit v1.2.1