| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | Re: \d with triggers: more than one row returned by a subquery used as an expression |
| Date: | 2021-12-22 21:03:08 |
| Message-ID: | 20211222210308.GD17618@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 17, 2021 at 09:43:56AM -0600, Justin Pryzby wrote:
> I want to mention that the 2nd problem I mentioned here is still broken.
> https://www.postgresql.org/message-id/20210717010259.GU20208@telsasoft.com
>
> It happens if non-inheritted triggers on child and parent have the same name.
This is the fix I was proposing
It depends on pg_partition_ancestors() to return its partitions in order:
this partition => parent => ... => root.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-psql-fix-d-for-statement-triggers-with-same-name-on-.patch | text/x-diff | 3.0 KB |
| 0002-psql-Add-newlines-and-spacing-in-trigger-query-for-d.patch | text/x-diff | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-12-22 21:33:28 | Re: do only critical work during single-user vacuum? |
| Previous Message | Peter Geoghegan | 2021-12-22 19:57:46 | Re: track_io_timing default setting |