| From: | Philip Alger <paalger0(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Cary Huang <cary(dot)huang(at)highgo(dot)ca>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement |
| Date: | 2025-10-21 17:53:34 |
| Message-ID: | CAPXBC8+J3o-EjCRv7+ppRjCJGZD7RH3NdSkj5e2-dprtY8rw-Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Just ignore it if you're pretty sure the error is unrelated. The
> cfbot cycles through all open patches and will re-run CI for yours
> in a day or three (not sure of the exact cycle time right now).
> If the same error persists then you'd better look closer.
>
Thanks Tom.
Actually, it's funny because it ran the first time for v7 all green on the
18th, then yesterday failed during a NetBSD Meson test for
`test_json_parser/002_inline`, which is unrelated to this patch. Can I
blame it on AWS East? lol.
--
Best,
Phil Alger
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-10-21 18:26:06 | Re: Question for coverage report |
| Previous Message | Peter Eisentraut | 2025-10-21 17:39:39 | Re: CI: Add task that runs pgindent |