| 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 04:55:11 |
| Message-ID: | 37ed240d0611062055r5d3e4652p733f5e413f7fc4ad@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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:
Triggers:
y AFTER DELETE ON x FOR EACH ROW EXECUTE PROCEDURE do_something()
Disabled triggers:
z BEFORE INSERT ON x FOR EACH ROW EXECUTE PROCEDURE input_stuff()
The patch compiled and tested cleanly on my machine, and passed all
regression tests.
I didn't find any relevant documentation that needed patching, so this
feature add should work fine as a standalone patch.
Regards,
BJ
| Attachment | Content-Type | Size |
|---|---|---|
| describe.c.diff | application/octet-stream | 3.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2006-11-07 05:21:46 | Re: [HACKERS] Indicate disabled triggers in \d |
| Previous Message | ITAGAKI Takahiro | 2006-11-07 04:02:31 | Re: Introducing an advanced Frequent Update Optimization |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2006-11-07 05:21:46 | Re: [HACKERS] Indicate disabled triggers in \d |
| Previous Message | David Fetter | 2006-11-06 23:44:06 | Re: Indicate disabled triggers in \d |