From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | a(dot)maclean(at)cas(dot)edu(dot)au |
Cc: | justin <justin(at)emproshunts(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgresql-8.3.7 unexpected connection closures |
Date: | 2009-06-23 00:41:08 |
Message-ID: | 1245717668.32535.4.camel@tillium.localnet |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2009-06-23 at 09:28 +1000, Andrew Maclean wrote:
> [snipity snip snip]
>
> Notwithstanding all the previous discussion. I still think there is a
> problem with postgresql on windows.
I agree, but you don't seem to be prepared take any steps to diagnose
what Pg might be interacting with to cause the problem.
This doesn't happen on all Windows installs. What makes yours different?
If we remove things that make it different from the default, does the
problem go away? If so, after what component was removed did the problem
go away?
If you won't help test by removing your AV software and checking if the
problem goes away, nobody can really help you since you're not willing
to go through any sort of fault isolation / diagnostic process.
Nobody here can wave a magic wand and make the problem go away; it's
going to take work on your side to help collect information that might
help identify the cause and lead to a fix.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Gerry Reno | 2009-06-23 00:48:38 | Re: Replication |
Previous Message | Greg Smith | 2009-06-23 00:35:41 | Re: Replication |