its own list of
dependent libraries) on one platform with one selected dynamic loading
API, I cannot say I recommend it. This would aid neither portability,
debug-ability, or performance (though compared to the overhead of SSL,
the jump table is kinda irrelevant).
..I didn't find any
opensource program which uses it.
-Seth Robertson
in-pgsql-hack...@baka.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
that file anyway?)
-Seth Robertson
in-pgsql-hack...@baka.org
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
In message <12314.1241809...@sss.pgh.pa.us>, Tom Lane writes:
Seth Robertson writes:
> In message <8766.1241799...@sss.pgh.pa.us>, Tom Lane writes:
>> Hmm, shouldn't we fix *that* rather than inventing a hack like this?
> Basically doing
In message <8766.1241799...@sss.pgh.pa.us>, Tom Lane writes:
Seth Robertson writes:
> I had a situation where I needed to connect to multiple postgresql
> servers in a variety of programs written in a variety of languages,
> including some which connected to mult
, the complexity of the
patch could be increased by using DNS to try and discover a canonical
name for the host. Using the IP address is another option, but is
probably not preferred since it reduces flexibility.
I can provide an 8.3 patch if anyone desires.
