Re: [HACKERS] Indicate disabled triggers in \d - Mailing list pgsql-patches

From Brendan Jurd
Subject Re: [HACKERS] Indicate disabled triggers in \d
Date
Msg-id 37ed240d0611062121u6bf68d64n4ddf505fa9108797@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Indicate disabled triggers in \d  ("Brendan Jurd" <direvus@gmail.com>)
Responses Re: [HACKERS] Indicate disabled triggers in \d
Re: [HACKERS] Indicate disabled triggers in \d
Re: [HACKERS] Indicate disabled triggers in \d
List pgsql-patches
On 11/7/06, Brendan Jurd <direvus@gmail.com> wrote:
> As discussed briefly on pgsql-hackers, the current psql \d command
> does not make any distinction between enabled and disabled triggers.
>
> The attached patch modifies psql's describeOneTableDetails() such that
> triggers and disabled triggers are displayed as two separate footer
> lists, for example:
>

Minor fix to the previous patch; result7 was not being cleared at the
end of the block.

Attachment

pgsql-patches by date:

Previous
From: "Brendan Jurd"
Date:
Subject: Re: [HACKERS] Indicate disabled triggers in \d
Next
From: "Peter Harris"
Date:
Subject: BUG #2741: Double-free on error in ECPGconnect