| From: | Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SQL:2011 application time |
| Date: | 2023-11-09 17:15:31 |
| Message-ID: | ba5694b7-cc5f-432f-8815-2d535a6dc95e@illuminatedcomputing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/9/23 05:47, Peter Eisentraut wrote:
> I went over the patch
> v17-0001-Add-temporal-PRIMARY-KEY-and-UNIQUE-constraints.patch in more
> detail
Thanks Peter!
I'm about halfway through jian he's last two emails. I'll address your
feedback also. I wanted to reply to this without waiting though:
> Overall, with these fixes, I think this patch is structurally okay. We
> just need to make sure we have all the weird corner cases covered.
One remaining issue I know about is with table partitions whose column
order has changed. I've got an in-progress fix for that, but I've been
prioritizing reviewer feedback the last few months. Just want to make
sure you know about it for now.
Thanks!
--
Paul ~{:-)
pj(at)illuminatedcomputing(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kumar, Sachin | 2023-11-09 17:35:01 | Re: pg_upgrade failing for 200+ million Large Objects |
| Previous Message | Tom Lane | 2023-11-09 16:57:47 | Re: Cleaning up array_in() |