Re: [HACKERS] Indicate disabled triggers in \d

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Brendan Jurd <direvus(at)gmail(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, 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: 2007-01-20 21:21:25
Message-ID: 200701202121.l0KLLPD11747@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Patch applied by Neil. Thanks.

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

Brendan Jurd wrote:
> 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, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-01-20 21:29:33 Simplifying pg_am representation of index sortability
Previous Message Tom Lane 2007-01-20 18:11:50 Re: Windows buildfarm failures

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-01-20 21:44:27 Re: [HACKERS] wal buffers documentation -errata
Previous Message Bruce Momjian 2007-01-20 18:49:39 Re: [PATCHES] currentItemData refactoring