| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: range_agg with multirange inputs |
| Date: | 2022-03-28 20:17:34 |
| Message-ID: | CAM-w4HMjrXxXAx=7ThBU8Kw5LiZRvYypm6LdJvoGGC4zbfb04A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fwiw the cfbot is failing due to a duplicate OID. Traditionally we
didn't treat duplicate OIDs as reason to reject a patch because
they're inevitable as other patches get committed and the committer
can just renumber them.
I think the cfbot kind of changes this calculus since it's a pain lose
the visibility into whether the rest of the tests are passing that the
cfbot normally gives us.
If it's not to much of a hassle could you renumber resubmit the patch
with an updated OID?
[10:54:57.606] su postgres -c "make -s -j${BUILD_JOBS} world-bin"
[10:54:57.927] Duplicate OIDs detected:
[10:54:57.927] 8000
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2022-03-28 20:21:17 | Re: [PATCH] Accept IP addresses in server certificate SANs |
| Previous Message | Greg Stark | 2022-03-28 20:11:55 | Re: Temporary tables versus wraparound... again |