| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
| Cc: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: alter function/procedure depends on extension |
| Date: | 2022-02-17 17:09:12 |
| Message-ID: | 202202171709.6ncyrg55ckot@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2022-Feb-17, Bryn Llewellyn wrote:
> qu. 1. What is the use-case for "alter function/procedure depends on extension"?
Suppose you have an extension that implements change auditing for
tables, which works by creating triggers on the audited tables. You
enable auditing for specific tables by calling one of the extension's
function; this function creates a trigger on the table.
The design idea was that if you drop the auditing extension, then those
triggers should be gone too.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"I'm always right, but sometimes I'm more right than other times."
(Linus Torvalds)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mladen Gogala | 2022-02-17 18:10:43 | 2 phase commit with FDW |
| Previous Message | Adrian Klaver | 2022-02-17 17:04:45 | Re: alter function/procedure depends on extension |