James Coleman writes:
> On Mon, Sep 21, 2020 at 11:36 AM Tom Lane wrote:
>> The recommended way to deal with updates these days is to leave the
>> original extension script as-is and just write update scripts
>> (1.0--1.1, 1.1--1.2, etc). That way, application of the updates
>> is tested automat
On Mon, Sep 21, 2020 at 11:36 AM Tom Lane wrote:
>
> James Coleman writes:
> > If there's a better list than this, please let me know, but I figured
> > hackers is appropriate since the extension building infrastructure is
> > documented in core.
>
> > While working on an in-house extension I rea
James Coleman writes:
> If there's a better list than this, please let me know, but I figured
> hackers is appropriate since the extension building infrastructure is
> documented in core.
> While working on an in-house extension I realized that while PGXS
> provides the standard regression test i
If there's a better list than this, please let me know, but I figured
hackers is appropriate since the extension building infrastructure is
documented in core.
While working on an in-house extension I realized that while PGXS
provides the standard regression test infrastructure, I'm not aware of
a
