On Thu, Sep 24, 2015 at 11:19:42PM +0300, Vadim Zhukov wrote: > 2015-09-24 22:58 GMT+03:00 Landry Breuil <lan...@rhaalovely.net>: > > On Thu, Sep 24, 2015 at 10:58:43AM -0700, patrick keshishian wrote: > >> On 9/23/15, Landry Breuil <lan...@rhaalovely.net> wrote: > >> > On Thu, Sep 24, 2015 at 07:50:15AM +0200, Landry Breuil wrote: > >> >> On Tue, Sep 22, 2015 at 10:28:37PM -0700, patrick keshishian wrote: > >> >> > On 9/19/15, Landry Breuil <lan...@rhaalovely.net> wrote: > >> >> > > On Fri, Sep 18, 2015 at 11:50:19PM -0700, patrick keshishian wrote: > >> >> > >> On 9/17/15, Landry Breuil <lan...@rhaalovely.net> wrote: <snip> > > > > Maybe to be brought upstream, but they probably dont care and like > > having a greedy-memory behaviour on linux where limits are ... > > mostly unlimited. > > > > Re database encoding, i was meaning that the module could default to > > create databases using UTFcrap, instead of the default SQL_ASCII we use > > now. To be tested on the other ports using the module, but i doubt > > there would be fallout. > > > > Vadim ? > > I don't think there would be any problems, and since it won't break > bulk builds anyway, I'll happily commit the postgresql.port.mk bits > right now. :)
Causes no fallout on geo/postgis & geo/pgrouting test suite :) Landry
