Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Date
Msg-id CABUevEwux0qYWOarQO1BNGKyjP+-OhLqd905yAePU4hOhKaFtQ@mail.gmail.com
Whole thread Raw
In response to Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]  (Craig Ringer <craig@2ndQuadrant.com>)
Responses Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
List pgsql-hackers
<p dir="ltr"><br /> On Jan 21, 2013 3:06 AM, "Craig Ringer" <<a
href="mailto:craig@2ndquadrant.com">craig@2ndquadrant.com</a>>wrote:<br /> ><br /> > On 01/21/2013 10:03 AM,
CraigRinger wrote:<br /> > > On 01/19/2013 04:08 AM, Boszormenyi Zoltan wrote:<br /> > >> However, I am
notsure whether Cygwin provides the mkstemp() call or not.<br /> > >> Searching... Found bugzilla reports
againstmkstemp on Cygwin.<br /> > > Is Cygwin a platform that should be targeted for the server backend<br />
>> these days?<br /> > ><br /> > > I can understand making sure that libpq works on Cygwin, but is
there<br/> > > any reason at all to run a Pg server backend on Cygwin rather than as<br /> > > native
Windowsbinaries?<br /> ><br /> > I'm not suggesting immediately dropping working support, since this is<br />
>so trivially worked around. I'm just wondering why anybody cares about<br /> > the platform.<p dir="ltr">I have
suggestedsimilar before, and been voted down :) iirc Andrew uses it, no? Either way, the consensus earlier had been
thatas long as it doesn't require major surgery or blocks something else, we should try to keep it working. And as you
saythis sounds like something that can be handled trivially, I think now is not the time. <p dir="ltr">/Magnus  

pgsql-hackers by date:

Previous
From: Миша Тюрин
Date:
Subject: standby, pg_basebackup and last xlog file
Next
From: Pavan Deolasee
Date:
Subject: Re: Removing PD_ALL_VISIBLE