|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Justin Pryzby <pryzby(at)telsasoft(dot)com>|
|Cc:||Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, 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|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
>> Is there any reason why WITH ORDINALITY can't work ?
>> This is passing the smoke test.
> How hard did you try to break it? It still seems to me that
> this can be fooled by an unrelated trigger with the same tgname.
Hmm ... no, it does work, because we'll stop at the first trigger
with tgparentid = 0, so unrelated triggers further up the partition stack
don't matter. But this definitely requires commentary. (And I'm
not too happy with burying such a complicated thing inside a conditional
inside a printf, either.) Will see about cleaning it up.
regards, tom lane
|Next Messagefirstname.lastname@example.org||2022-01-18 01:08:01||RE: drop tablespace failed when location contains .. on win32|
|Previous Message||Jelte Fennema||2022-01-18 00:35:36||Re: [EXTERNAL] Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings|