Re: Extensions, patch v18 (merge against master, bitrot-only-fixes) - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)
Date
Msg-id m28vzpmluh.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> However, the only way I can see to fix this "automatically" is to have
>> the makefiles propagate PG_VERSION_NUM (or one of the other values set
>> by configure) into generated control files.
>
> Ah, somewhat like what I was asked to remove from the patch, right?

I've been pointed off-list that this message ain't conveying the meaning
I'm attaching it, sorry about that. What I mean is that should we change
our opinion again the code to do that has already been written.

Allow me to insist on "we": it's not like I feel forced into changing
the design again and again, I realise I'm acting eagerly upon group
decision making steps before to ensure it's the final step. Well, we all
have been reading over-stressed exchanges on this list before, right? :)

Will now step back on the topic, or try to...

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: clang and LLVM
Next
From: Josh Kupershmidt
Date:
Subject: Re: Default mode for shutdown