From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Adding OLD/NEW support to RETURNING |
Date: | 2024-03-27 15:28:22 |
Message-ID: | 38f040f01432fae89fe5247f4f34b74b95ac2948.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2024-03-27 at 13:19 +0000, Dean Rasheed wrote:
> What I'm most worried about now is that there are other areas of
> functionality like that, that I'm overlooking, and which will
> interact
> with this feature in non-trivial ways.
Agreed. I'm not sure exactly how we'd find those other areas (if they
exist) aside from just having more eyes on the code.
>
> So on reflection, rather than trying to rush to get this into v17, I
> think it would be better to leave it to v18.
Thank you for letting me know. That allows some time for others to have
a look.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2024-03-27 15:30:37 | Re: Introduce XID age and inactive timeout based replication slot invalidation |
Previous Message | Robert Haas | 2024-03-27 15:27:46 | Re: pgsql: Allow using syncfs() in frontend utilities. |