Re: libpq compression - Mailing list pgsql-hackers

From Tom Lane
Subject Re: libpq compression
Date
Msg-id 26825.1340206465@sss.pgh.pa.us
Whole thread Raw
In response to Re: libpq compression  (Florian Pflug <fgp@phlo.org>)
Responses Re: libpq compression  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Florian Pflug <fgp@phlo.org> writes:
> I wonder though if shouldn't restrict the allowed ciphers list to being
> a simple list of supported ciphers. If our goal is to support multiple
> SSL libraries transparently then surely having openssl-specific syntax
> in the config file isn't exactly great anyway...

No, we don't want to go there, because then we'd have to worry about
keeping the default list in sync with what's supported by the particular
version of the particular library we chance to be using.  That's about
as far from transparent as you can get.  A notation like "DEFAULT"
is really quite ideal for our purposes in that respect.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Pg default's verbosity?
Next
From: "Kevin Grittner"
Date:
Subject: Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node