Re: ecpg thread-safe descriptor - Mailing list pgsql-patches

From Tom Lane
Subject Re: ecpg thread-safe descriptor
Date
Msg-id 26528.1191355626@sss.pgh.pa.us
Whole thread Raw
In response to Re: ecpg thread-safe descriptor  (Magnus Hagander <magnus@hagander.net>)
Responses Re: ecpg thread-safe descriptor  (Michael Meskes <meskes@postgresql.org>)
List pgsql-patches
Magnus Hagander <magnus@hagander.net> writes:
> Michael Meskes wrote:
>> So, does an explicit export list help? If so I'm all for it. There is no
>> need to export all symbols. I always tried to keep the number of symbols
>> that get exported but are not needed low. So this will give the best
>> result possible.

> Yeah, it does seem to fix it.

That's very good news.  If Michael can put together an export list
soon then we'll be in good shape.

Michael: you should bump the major version number of ecpglib when you do
this.  Removing the not-officially-exported visible symbols *is* an ABI
break.  You may think there isn't anything depending on them, but
remember how we thought that (twice) for libpq too.  Bumping the major
version number will be cheap insurance against complaints later.

            regards, tom lane

pgsql-patches by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: ecpg thread-safe descriptor
Next
From: Hannes Eder
Date:
Subject: minor compiler warning in libpg/fe-secure.c on win32 (msvc)