Re: Breaking compile-time dependency cycles of Postgres subdirs?

From: Christian Convey <christian(dot)convey(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Breaking compile-time dependency cycles of Postgres subdirs?
Date: 2014-02-10 15:37:53
Message-ID: CAPfS4Zykb-HzUS2Lcm3V5WB2xT3C0oZuhKx9pser7E0Th=XOzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 10, 2014 at 10:28 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I think if it had been a clear, enforced goal all along, it might've been
> possible to build the system with such a restriction (for the most part at
> least). At this point though, the amount of work and code churn involved
> seems like it'd far exceed the benefits.
>
>
That makes sense to me. I certainly didn't think it was a slam-dunk that
what I was proposing would be an improvement. It just seemed like a
question worth asking. Thanks for your thoughts.

- Christian

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-02-10 16:11:28 Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Previous Message Tom Lane 2014-02-10 15:28:40 Re: Breaking compile-time dependency cycles of Postgres subdirs?