From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, alvherre(at)alvh(dot)no-ip(dot)org |
Subject: | Re: Support json_errdetail in FRONTEND builds |
Date: | 2024-03-15 22:23:07 |
Message-ID: | F93F2ABC-1F41-4E82-BD00-58013A160054@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 15 Mar 2024, at 21:56, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On Fri, Mar 15, 2024 at 10:15 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
> Daniel Gustafsson <daniel(at)yesql(dot)se <mailto:daniel(at)yesql(dot)se>> writes:
> > I can't see how refusing to free memory owned and controlled by someone else,
> > and throwing an error if attempted, wouldn't be a sound defensive programming
> > measure.
>
> I think the argument is about what "refusal" looks like.
> An Assert seems OK to me, but anything based on elog is
> likely to be problematic, because it'll involve exit()
> somewhere.
>
> Yeah, I agree an Assert seems safest here.
>
> I'd like to get this done ASAP so I can rebase my incremental parse patchset. Daniel, do you want to commit it? If not, I can.
Sure, I can commit these patches. It won't be until tomorrow though since I
prefer to have ample time to monitor the buildfarm, if you are in a bigger rush
than that then feel free to go ahead.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2024-03-15 22:30:51 | Re: Statistics Import and Export |
Previous Message | Andres Freund | 2024-03-15 21:14:49 | Re: BitmapHeapScan streaming read user and prelim refactoring |