Re: pg_get_triggerdef - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: pg_get_triggerdef
Date
Msg-id 200303201858.h2KIw6E01091@candle.pha.pa.us
Whole thread Raw
In response to pg_get_triggerdef  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-patches
Newer patch applied with doc patch.  Thanks.

---------------------------------------------------------------------------



Christopher Kings-Lynne wrote:
> This patch creates a function named pg_get_triggerdef that takes the oid of
> a trigger as its parameter.  It is basically copied from the pg_dump code.
>
> Once we're certain it's perfect, we could probably save some effort in
> pg_dump by using the function.
>
> Once it's committed, I will be modifying psql to show trigger definitions,
> instead of just the name.
>
> I have tested it with a bunch of different triggers, parameters, constraint
> triggers, weird names, different functions, etc and it seems to be OK.
>
> Cheers,
>
> Chris

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Simplify clusterdb
Next
From: Bruce Momjian
Date:
Subject: Re: pg_get_triggerdef #2