From: | Dent John <denty(at)qqdd(dot)eu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Use of reloptions by EXTENSIONs |
Date: | 2019-06-24 09:47:09 |
Message-ID: | 10B434FE-090D-45AF-9899-89420025EE1A@qqdd.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thank you, Tom.
(And sorry for the delay following up.)
I’ve marked myself down for review for this patch in the next CF.
I’ll see if I can get the patch applied and feed back on how much it move towards making my use case a viable proposition.
d.
> On 9 Jun 2019, at 17:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Dent John <denty(at)qqdd(dot)eu> writes:
>> I guess my question is, and I correctly understanding that reloptions are basically off-limits to EXTENSIONS?
>
> IIRC that's basically true. There's a lot of dissatisfaction with the
> current implementation of reloptions, although I think that it's been
> mainly focused on the fact that adding new ones is hard/error-prone
> even within the core code. If you want to help move this along, you
> could review the existing patch in the area:
>
> https://www.postgresql.org/message-id/flat/2083183(dot)Rn7qOxG4Ov(at)x200m
>
> and/or propose additional changes.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dagfinn Ilmari Mannsåker | 2019-06-24 10:03:20 | Re: using explicit_bzero |
Previous Message | John Naylor | 2019-06-24 09:21:33 | Re: benchmarking Flex practices |