In the SSL code in libpq it does some processing with DH parameters:
SSL_CTX_set_tmp_dh_callback()
This function is marked as server use only[1], the client always uses
the DH parameters in the server, so all the code in the client dealing
with the DH parameters is useless. This patch removes
Martijn van Oosterhout kleptog@svana.org writes:
It's not clear why the code was added in the first place,
I thought it was there to support client-side authentication (ie,
verifying the server's certificate). We don't support that right
now but we ought to.
regards,
On Wed, Apr 12, 2006 at 10:00:29AM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
It's not clear why the code was added in the first place,
I thought it was there to support client-side authentication (ie,
verifying the server's certificate). We don't support that
This patch makes pg_dump wrap insert dumps (-d, -D) in a transaction to
speed the restore process. It also adds an option to disable these
transactions for doing things like copying only newly inserted values from
one database to another (assuming old ones will fail on an unique
Kris Jurka [EMAIL PROTECTED] writes:
This patch makes pg_dump wrap insert dumps (-d, -D) in a transaction to
speed the restore process.
What's the point of this, compared to Simon's recent patch adding an
option to wrap the whole output in one big transaction? An intermediate
level doesn't
