Skip site navigation (1) Skip section navigation (2)

Re: libpq API incompatibility between 7.4 and 8.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>,Martin Pitt <mpitt(at)debian(dot)org>
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Date: 2005-02-04 21:41:51
Message-ID: 17633.1107553311@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> In short, fixing this the way Bruce wants to will be a nontrivial amount
>> of effort.

> psql actually calls get_progname().  Do we know that it will try to link
> in the other functions from path.c?  I am unsure.

I don't know of any commonly used linkers that link at granularity finer
than one source file, and in any case for shared libraries the library
is all-or-nothing.

Grep shows that 7.4 psql does reference is_absolute_path, and 7.4
pg_dumpall does reference last_path_separator, so at least three of the
four are at issue.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-02-04 22:02:07
Subject: Re: Escaping the ARC patent
Previous:From: Jim C. NasbyDate: 2005-02-04 21:35:59
Subject: Re: Escaping the ARC patent

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-02-05 01:05:15
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Previous:From: Bruce MomjianDate: 2005-02-04 21:33:39
Subject: Re: libpq API incompatibility between 7.4 and 8.0

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group