Re: includedir_internal headers are not self-contained

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christoph Berg <cb(at)df7cb(dot)de>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: includedir_internal headers are not self-contained
Date: 2014-05-02 01:33:02
Message-ID: 20140502013302.GC6018@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I wrote:
> > How about we change common/relpath.[hc] to export a single version of
> > relpath() that takes its arguments as separate plain OIDs, and then
> > make the other versions wrappers that are only declared in some
> > backend header? The wrappers could possibly be macros, allowing
> > things like pg_xlogdump to keep using them as long as they didn't
> > mind importing backend headers. (Though for the RelFileNode case this
> > would imply multiple evaluation of the macro argument, so maybe it's
> > not such a great idea.)
>
> Since nobody objected, I've committed something along this line.
> include/common/ is now free of references to backend headers.

Many thanks for the extra effort.

> The patch is certainly too invasive to consider back-patching into
> 9.3, though.

I feel unsure about this. I agree the patch is quite invasive. Leaving
9.3 in a broken state seems problematic. In particular I'm not sure
what would Debian do about the whole issue; would they have to carry the
patch for their 9.3 packages?

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-02 01:40:51 Re: includedir_internal headers are not self-contained
Previous Message Noah Misch 2014-05-02 01:24:56 Re: Obsolete coding in fork_process.c