Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Indicate disabled triggers in \d

From: "Brendan Jurd" <direvus(at)gmail(dot)com>
To: "David Fetter" <david(at)fetter(dot)org>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Indicate disabled triggers in \d
Date: 2006-11-07 05:21:46
Message-ID: 37ed240d0611062121u6bf68d64n4ddf505fa9108797@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On 11/7/06, Brendan Jurd <direvus(at)gmail(dot)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: describe.c.diff
Description: application/octet-stream (4.0 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2006-11-07 05:31:14
Subject: Re: Introducing an advanced Frequent Update Optimization
Previous:From: Brendan JurdDate: 2006-11-07 04:55:11
Subject: Re: [HACKERS] Indicate disabled triggers in \d

pgsql-patches by date

Next:From: Peter HarrisDate: 2006-11-07 14:31:57
Subject: BUG #2741: Double-free on error in ECPGconnect
Previous:From: Brendan JurdDate: 2006-11-07 04:55:11
Subject: Re: [HACKERS] Indicate disabled triggers in \d

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group