Re: Slony 1.1.5 en Solaris

On 9/21/06, Roberto Andrade Fonseca <randrade(at)inteligentes(dot)com(dot)mx> wrote:
> Hola:
> Slony 1.1.5 me dice que hay que instalarle un parche pero el parche es
> para la version 7.4.2: threadsafe-libpq-742.diff.gz
>

extraido de http://slony1.projects.postgresql.org/slony_115/faq.html:
"
On AIX and Solaris (and possibly elsewhere), both Slony-I and
PostgreSQL must be compiled with the --enable-thread-safety option.
The above results when PostgreSQL isn't so compiled.

What breaks here is that the libc (threadsafe) and libpq
(non-threadsafe) use different memory locations for errno, thereby
leading to the request failing.

Problems like this crop up with disadmirable regularity on AIX and
Solaris; it may take something of an "object code audit" to make sure
that ALL of the necessary components have been compiled and linked
with --enable-thread-safety.

For instance, I ran into the problem one that LD_LIBRARY_PATH had been
set, on Solaris, to point to libraries from an old PostgreSQL compile.
That meant that even though the database had been compiled with
--enable-thread-safety, and slon had been compiled against that, slon
was being dynamically linked to the "bad old thread-unsafe version,"
so slon didn't work. It wasn't clear that this was the case until I
ran ldd against slon.

Note that with libpq version 7.4.2, on Solaris, a further thread patch
was required; similar is also required for PostgreSQL version 8.0.
"
> ¿Existe un parche para 8.x?
>

nada me dice que si... es probable que tengas que hacerlo tu mismo...
mejor pregunta en la lista de slony y nos cuentas

--
Atentamente,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
Richard Cook