Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229])
	by mail.postgresql.org (Postfix) with ESMTP id 54EE88B63D8
	for <pgsql-hackers@postgresql.org>;
	Wed, 20 Jun 2012 12:50:14 -0300 (ADT)
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1ShNAZ-0000eE-9t
	for pgsql-hackers@postgresql.org; Wed, 20 Jun 2012 15:50:13 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q5KFnpDc027149;
	Wed, 20 Jun 2012 11:49:51 -0400 (EDT)
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
cc: Florian Pflug <fgp@phlo.org>, Robert Haas <robertmhaas@gmail.com>,
	Martijn van Oosterhout <kleptog@svana.org>,
	Magnus Hagander <magnus@hagander.net>,
	Euler Taveira <euler@timbira.com>, Bruce Momjian <bruce@momjian.us>,
	Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: libpq compression
In-reply-to: <1340204219-sup-2061@alvh.no-ip.org>
References: 
 <CABUevEzVpqS5RCLz2fFREdPFkuYkEKsrMpnfPixYWPki2=iJOA@mail.gmail.com>
	<4FDB954F.9010606@timbira.com> <5136.1339799120@sss.pgh.pa.us>
	<5365.1339799869@sss.pgh.pa.us>
	<CABUevEz_V4YYc0tUhkC6KD2GddysM5Z76pcHcMYiMDd7dwMxVQ@mail.gmail.com>
	<11357.1339822502@sss.pgh.pa.us>
	<CABUevEy1sUTOeCjNicUggnMpT7MfgjWud8kQ=wkvJsfbCU8=WQ@mail.gmail.com>
	<19804.1339859730@sss.pgh.pa.us>
	<9B10BD6E-31AA-4699-BB67-5C386B623F77@phlo.org>
	<27043.1339950593@sss.pgh.pa.us> <20120618174233.GA24681@svana.org>
	<CA+TgmoaTMxcAFMN8d_FXD1S_3keyq3a=Vwa7ka8cnVepy-jqjg@mail.gmail.com>
	<1D8B2B60-F42E-448C-9295-C07FACCF0611@phlo.org>
	<1340204219-sup-2061@alvh.no-ip.org>
Comments: In-reply-to Alvaro Herrera <alvherre@commandprompt.com>
	message dated "Wed, 20 Jun 2012 11:03:40 -0400"
Date: Wed, 20 Jun 2012 11:49:51 -0400
Message-ID: <27148.1340207391@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201206/1163
X-Sequence-Number: 210003

Alvaro Herrera <alvherre@commandprompt.com> writes:
> I looked at the code (apps/ciphers.c) and it looks pretty easy to obtain
> the list of ciphers starting from the stringified configuration
> parameter and iterate on them.

Do you mean that it will produce an expansion of the set of ciphers
meeting criteria like "!aNULL"?  If so, I think we are set; we can
easily check to see if the active cipher is in that list, no?

			regards, tom lane