Wait, what?  I actually removed new_pgsql before I ran that last time.

...

Okay, that was weird.  Sorry about that - I guess I pulled the wrong command
from history.  After fixing my configure options, slony was successfully
configured.  Running make now.

The new_pgsql directory was another directory where I tried to install
postgres to, to see if a blank install (with threadsafe enabled) would fix
the issue.  It didn't.

The Fix:

Note that this seems really strange, so I'm taking my own words with a grain
of salt (and so should everyone who reads this).

I still had the original postgres source directory, where I had first
extracted to, so I just re-ran ./configure with the new options, then ran
make, assuming everything would get overwritten with the new options.
 Apparently not.

Removing the directory, extracting the tarball anew, and then doing a new
configure, make, and make install did work.  So I guess I'll just need to
remember to start from scratch next time.
---
===========================
Samuel Nelson
Consistent State
www.consistentstate.com
303-955-0509
===========================


On Tue, Jul 12, 2011 at 11:15 AM, Steve Singer <ssinger at ca.afilias.info>wrote:

> On 11-07-12 12:52 PM, Sam Nelson wrote:
>
>> Sure.  Here it is.
>> ---
>> ===========================
>> Samuel Nelson
>> Consistent State
>> www.consistentstate.com <http://www.consistentstate.**com<http://www.consistentstate.com>
>> >
>> 303-955-0509
>> ===========================
>>
>
> configure is linking the version in /usr/local/new_pgsql/lib
> Based on the output in your config.log I don't think that version of libpq
> has thread safety enabled.
>
> It also seems strange that you are using some things from
> /usr/local/new_pgsql and some things from /usr/local/pgsql
>
>
>
>
>>
>> On Tue, Jul 12, 2011 at 9:53 AM, Steve Singer <ssinger at ca.afilias.info
>> <mailto:ssinger at ca.afilias.**info <ssinger at ca.afilias.info>>> wrote:
>>
>>    On 11-07-12 11:51 AM, Sam Nelson wrote:
>>
>>        Well, I checked the output of that command and it didn't look
>>        right, so
>>        I removed all postgres directories (everything except the postgres
>>        cluster) in /usr/local/pgsql and deleted the old postgresql install
>>        directory, extracted the tarball again, re-configured postgres, and
>>        tried again.  This time, I got what I was expecting from pg_config:
>>
>>        $ /usr/local/pgsql/bin/pg_config --configure
>>        '--with-python' '--with-perl' '--enable-thread-safety'
>>        '--prefix=/usr/local/pgsql'
>>
>>
>>    Can I see the config.log file that configure generates?
>>
>>
>>
>>        However, even after doing the above and
>>        adding --with-pgconfigdir=/usr/local/**__pgsql/bin, Slony refuses
>> to
>>        configure.  It still comes back saying configure: error:
>>        PQisthreadsafe
>>        test failed - PostgreSQL needs to be compiled with
>>        --enable-thread-safety
>>        ---
>>        ===========================
>>        Samuel Nelson
>>        Consistent State
>>        www.consistentstate.com <http://www.consistentstate.**com<http://www.consistentstate.com>
>> >
>>        <http://www.consistentstate.__**com <http://www.consistentstate.**
>> com <http://www.consistentstate.com>>>
>>
>>        303-955-0509 <tel:303-955-0509>
>>
>>        ===========================
>>
>>
>>        On Tue, Jul 12, 2011 at 2:48 AM, Jan Wieck <JanWieck at yahoo.com
>>        <mailto:JanWieck at yahoo.com>
>>        <mailto:JanWieck at yahoo.com <mailto:JanWieck at yahoo.com>>> wrote:
>>
>>            On 7/11/2011 6:13 PM, Sam Nelson wrote:
>>
>>                Hrm.  Didn't seem to help.
>>
>>                I did have a few different libpq's on the testing VMs we
>>        have
>>                set up, so
>>                I removed them all.  Now, find / -name '*libpq*' (as
>>        root) only
>>                finds
>>                the instance that has been installed with thread safety.
>>
>>                I even tried using --enable-thread-safety-force (and
>>        then, as per
>>                postres's configure instructions, testing for thread
>>        safety with the
>>                binary in src/test/thread/, which came back saying the
>>        system
>>                was thread
>>                safe).  Still no luck.
>>
>>                I'm using the following flags for slony's ./configure
>>        script:
>>                --prefix=/usr/local/pgsql/
>>        --with-pgbindir=/usr/local/___**_pgsql/bin/
>>                --with-pglibdir=/usr/local/___**_pgsql/lib/
>>
>>                Do I need anything more than that?
>>
>>
>>            What is the output of
>>
>>                /usr/local/pgsql/bin/pg_config --configure
>>
>>            and did you try
>>
>>                ./configure --with-pgconfigdir=/usr/local/**____pgsql/bin
>>
>>
>>            Jan
>>
>>            --
>>            Anyone who trades liberty for security deserves neither
>>            liberty nor security. -- Benjamin Franklin
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20110712/84696b3d/attachment.htm