From xach at xach.com Fri Aug 31 16:32:42 2012 From: xach at xach.com (Zach Beane) Date: Fri, 31 Aug 2012 12:32:42 -0400 Subject: [postmodern-devel] Unix socket directory configuration Message-ID: <878vcvkonp.fsf@zpobx.site.sys> Hi, I'm trying to use Postmodern on Linux with a Postgres built from scratch. The default value for the Unix socket directory in that situation is /tmp. Postmodern defaults it to /var/run/postgresql, which is more typical for a vendor-packaged Postgres on Linux. It's easy enough to alter/bind cl-postgres::*unix-socket-dir* as needed, but I'm always a little reluctant to use ::. Is that variable a candidate for adding to the supported API by exporting its name? Thanks, Zach From xach at xach.com Fri Aug 31 16:42:04 2012 From: xach at xach.com (Zach Beane) Date: Fri, 31 Aug 2012 12:42:04 -0400 Subject: [postmodern-devel] Unix socket directory configuration In-Reply-To: <878vcvkonp.fsf@zpobx.site.sys> (Zach Beane's message of "Fri, 31 Aug 2012 12:32:42 -0400") References: <878vcvkonp.fsf@zpobx.site.sys> Message-ID: <874nnjko83.fsf@zpobx.site.sys> Zach Beane writes: > Hi, > > I'm trying to use Postmodern on Linux with a Postgres built from > scratch. The default value for the Unix socket directory in that > situation is /tmp. Postmodern defaults it to /var/run/postgresql, which > is more typical for a vendor-packaged Postgres on Linux. > > It's easy enough to alter/bind cl-postgres::*unix-socket-dir* as needed, > but I'm always a little reluctant to use ::. Is that variable a > candidate for adding to the supported API by exporting its name? For what it's worth, the the C client library handles this by checking to see if the host starts with a "/", and uses it for the socket directory if so. Postmodern uses the keyword :unix instead. Zach