Re: htup header reorganization breaks many extension modules - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: htup header reorganization breaks many extension modules
Date
Msg-id CAB7nPqRbr2DE9XmozRvh_WuD6vUmbS_30OYHZD6iTt5r7pCGUg@mail.gmail.com
Whole thread Raw
In response to Re: htup header reorganization breaks many extension modules  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
List pgsql-hackers


On Wed, Sep 26, 2012 at 4:14 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
Hitoshi Harada wrote:
> On Tue, Sep 25, 2012 at 5:30 PM, Peter Eisentraut <peter_e@gmx.net>
wrote:
>> I haven't followed the details of the htup header reorganization, but
I
>> have noticed that a number of external extension modules will be
broken
>> because of the move of GETSTRUCT() and to a lesser extent
>> heap_getattr().  Of course some #ifdefs can fix that, but it seems
>> annoying to make everyone do that.  Maybe this could be reconsidered
to
>> reduce the impact on other projects.

> But it's only add #include "access/htup_details.h"?  I'd not argue
> it's harmful unless I missed your point.

I guess the point is that you need an #ifdef if you want a module
to be able to build with both 9.3 and lower versions.

Otherwise the compiler will complain about the missing include
file on older versions.
The modules of Postgres depend on the core and not the opposite, so isn't it the responsability
of the maintainers of the modules to insure that what they make is still compilable with postgres?
This can be simply fixed by providing, as mentionned, ifdefs controlled by PG_VERSION_NUM
including htup_details.h, so the correction effort is not that much...
--
Michael Paquier
http://michael.otacoo.com

pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Oid registry
Next
From: Виктор Егоров
Date:
Subject: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.