On Oct 20, 2014, at 5:03 PM, David E. Wheeler da...@justatheory.com wrote:
This another reason not to use KeepAlive, I guess. OnDemand is supposed to
fire up a job only when it’s needed. No idea what that means.
I think the idea of OnDemand is for launchd items to act a bit like inetd does:
On 28 Jul 2014, at 4:57 PM, Peter Geoghegan wrote:
[] Then
again, who knows? The Mac OS X behavior seems totally arbitrary to me.
If I had to guess I'd say it has something to do with their providing
an open standard shim to a UTF-16 based proprietary API.
A quick glance at OSX's
On 1 Apr 2014, at 11:38 PM, carriingfat...@ya.ru wrote:
I set certificate auth on postgresql 9.3. I generate SSL certificate with my
custom extension. So, OpenSSL read it, PostgreSQL accept it if this extension
is not critical, but if I set this extension critical, PostgreSQL deny
On 2 Apr 2014, at 5:43 PM, Tom Lane wrote:
I poked around a bit, and so far as I can tell, OS X does not store debug
symbol tables in executables. It looks like gdb goes to the .o files when
it wants debug info. What's in the .o files is good ol' DWARF (at least
in reasonably recent OS X
One comment, this:
/* get 128 random bits */
int err = px_get_random_bytes(buf, 16);
might be better to use px_get_pseudo_random_bytes(). UUIDs don't
need to be unguessable or have perfect entropy; they just need to
be collision-resistant. RFC4122 mentions this I think, and if you
look at
I applied both libpq.tls11plus.diff and the related
psql.conninfo.tlsver.diff patch to postgresql git head.
Source review:
The source changes are pretty tiny. Although I think the change
from TLSv1_method to SSLv23_method is correct, the comment is not
quite correct:
* SSLv23_method() is only
By an odd coincidence, I also decided to try to const-ify libpq
recently, and noticed this thread as I was cleaning up my patch for
submission. For what it's worth, I've attached my patch to this message.
It doesn't move as much data into the text segment as Oskari Saarenmaa's
patch does, but it
