Re: Perfomance degradation 9.3 (vs 9.2) for FreeBSD
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Palle Girgensohn <girgen@freebsd.org>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Robert Haas <robertmhaas@gmail.com>, Francois Tigeot <ftigeot@wolfpond.org>
Date: 2014-04-21T15:43:46Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add shared_memory_type GUC.
- f1bebef60ec8 12.0 landed
Hi, On 2014-04-21 17:39:39 +0200, Magnus Hagander wrote: > But do we really want a *guc* for it though? Isn't it enough (and in fact > better) with a configure switch to pick the implementation when multiple > are available, that could then be set by default for example by the freebsd > ports build? That's a lot less "overhead" to keep dragging around... Well, we don't know at all it's just freebsd that's affected. In fact, I would be surprised if there aren't other platforms that regressed due to this. I think a configure switch actually ends up being more code than the GUC... Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services