Re: postgresql-8.3.7 unexpected connection closures

From: "Andrew Maclean" <a(dot)maclean(at)cas(dot)edu(dot)au>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Craig Ringer'" <craig(at)postnewspapers(dot)com(dot)au>
Cc: "'General'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: postgresql-8.3.7 unexpected connection closures
Date: 2009-06-19 05:38:26
Message-ID: 00da01c9f0a0$2bb278c0$83176a40$@maclean@cas.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I would NEVER run a production server in windows!

These are just laptops/workstations that are used for development e.g, when
network connections are not available or when travelling. But these things
still shouldn't occur. I will also try the beta release on these machines to
see if it goes away.

Andrew

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, 19 June 2009 15:03
To: Craig Ringer
Cc: a(dot)maclean(at)cas(dot)edu(dot)au; General
Subject: Re: [GENERAL] postgresql-8.3.7 unexpected connection closures

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> I increasingly wonder if Symantec or McAfee can be persuaded to offer a
> buildfarm machine with their software to PostgreSQL. Virus scanners on
> servers are an (IMO nearly insane) fact of life on Windows, apparently,
> and certainly on Windows desktops that may also run PostgreSQL, so it
> needs to get along with them.

There's always the "friends don't let friends run servers on Windows"
approach.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2009-06-19 05:39:27 Re: postgresql-8.3.7 unexpected connection closures
Previous Message Tom Lane 2009-06-19 05:03:13 Re: postgresql-8.3.7 unexpected connection closures