Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement - Mailing list pgsql-hackers

From Philip Alger
Subject Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement
Date
Msg-id CAPXBC8L0Mgw=sa49UJsJZVtMWsWmPQDPsheMxEJKUtnqeXEuAg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement  (Jim Jones <jim.jones@uni-muenster.de>)
List pgsql-hackers
Hi Jim,

Just to add to this:
 
I don't think it's the expected behaviour. For instance,
pg_get_viewdef() sees it differently (opposite approach):

postgres=# SELECT pg_get_viewdef('"MyView"');
      pg_get_viewdef
---------------------------
  SELECT 42 AS "?column?";
(1 row)


I saw from the docs that pg_get_viewdef('name') is deprecated and instead users should use an OID: https://www.postgresql.org/docs/18/functions-info.html#FUNCTIONS-INFO-CATALOG


--
Best, Phil Alger

pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: failed NUMA pages inquiry status: Operation not permitted
Next
From: AIX PG user
Date:
Subject: Re: AIX support