| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | ahodgson(at)simkin(dot)ca, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |
| Date: | 2023-03-03 18:41:26 |
| Message-ID: | 2553512.1677868886@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2023-Mar-03, Tom Lane wrote:
>> Basically just make the recursive steps match on tgparentid instead
>> of name, like this.
> Thank you, looks sane to me.
OK, will work on getting it committed.
> I wonder how come this problem took so long to be detected with Ruby on
> Rails; it's been in released 13.x and 14.x for seven months now. I
> suppose it would be very useful if the Ruby on Rails community would run
> their tests more often on new Postgres versions (or even on the tip of
> stable branches).
Um ... 13.x and 14.x aren't showing the problem, or is there something
I missed? But I agree that it'd be good if we could get some Ruby folk
to test more promptly --- it's pretty sad that this didn't get noticed
sooner in v15.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-03-03 19:33:34 | Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |
| Previous Message | Alvaro Herrera | 2023-03-03 18:17:35 | Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails |