| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | pg_trigger.tgparentid |
| Date: | 2020-02-17 21:56:41 |
| Message-ID: | 20200217215641.GA29784@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
As mentioned in https://postgr.es/m/20191231194759.GA24692@alvherre.pgsql
I propose to add a new column to pg_trigger, which allows us to remove a
pg_depend scan when cloning triggers when adding/attaching partitions.
(It's not that I think the scan is a performance problem, but rather
than notionally we try not to depend on pg_depend contents for this kind
of semantic derivation.)
--
Álvaro Herrera 39°49'30"S 73°17'W
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Record-parents-of-triggers.patch | text/x-diff | 4.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2020-02-17 21:57:33 | Re: Duplicate words in comments |
| Previous Message | Tom Mercha | 2020-02-17 20:24:43 | SPI Concurrency Precautions? |