Re: [PATCH] Reduce noise from tsort

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCH] Reduce noise from tsort
Date: 2006-04-15 18:08:45
Message-ID: 20343.1145124525@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Sat, Apr 15, 2006 at 12:12:53PM -0400, Tom Lane wrote:
>> Personally I've been wondering for some time why we use lorder/tsort
>> at all. Are there any platforms we support where this is still needed?
>> (Given the existence of circular references within libpq.a, one would
>> think that tsort wouldn't help such a platform anyway.)

> I've never worked with a system that cared about the order within
> libraries so I've never really experienced the problem. But I leave it
> in because I figure it must fix something for someone somewhere...

Well, I vote we take it out, which would eliminate these warnings
instead of just shorten them. On a platform where tsorting a non-shared
library's contents is actually essential, libpq.a would be useless
anyway because of the circular internal references. Presumably,
anyone who's using Postgres on such a platform only cares about the .so
library. So I don't see any point in including the tsort step.

(AFAIK we inherited the tsort stuff from Berkeley; it may have been
useful once upon a time, but that was a long time ago.)

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-04-15 18:09:06 Re: Proposed doc-patch: Identifying the Current WAL file
Previous Message Tom Lane 2006-04-15 17:57:43 Re: Proposed doc-patch: Identifying the Current WAL file