Re: Use of reloptions by EXTENSIONs

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Dent John <denty(at)qqdd(dot)eu>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Use of reloptions by EXTENSIONs
Date: 2019-06-25 01:16:59
Message-ID: 20190625011659.GD5569@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 24, 2019 at 11:47:09AM +0200, Dent John wrote:
> 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.

There is another patch which provides more coverage for reloptions:
https://commitfest.postgresql.org/23/2064/

Based on my last lookup, I was rather unhappy with its shape because
of the assumptions behind the tests and the extra useless work it was
doing with parameter strings (the set of WARNING is also something we
don't need). If we get that first in, we can then make sure that any
extra refactoring has hopefully no impact.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ian Barwick 2019-06-25 01:57:58 Re: [PATCH] Stop ALTER SYSTEM from making bad assumptions
Previous Message Michael Paquier 2019-06-25 01:07:50 Re: check_recovery_target_lsn() does a PG_CATCH without a throw