On Fri, Jun 24, 2005 at 04:00:36PM -0400, Joe wrote:
> Richard Huxton wrote:
>
> > You will have (assuming the same as on *nix):
> > 1. Master process - starts all the others
> > 2. One backend per client
> > 3. Stats buffer/collector
> > 4. Auto-vacuum (optional, not really part of the main syste
Richard Huxton wrote:
> You will have (assuming the same as on *nix):
> 1. Master process - starts all the others
> 2. One backend per client
> 3. Stats buffer/collector
> 4. Auto-vacuum (optional, not really part of the main system yet)
It appears that, when started as a Windows service, four
Scott Goldstein <[EMAIL PROTECTED]> writes:
> I had a couple of questions about Postgres 8.0 on Windows platforms:
>
> 1. Has Postgres 8.0 seen many field deployments yet? What have been the
> results?
I have 8.0.2 in production with zero problems. It's not a high-load
installation but it's
Scott Goldstein wrote:
I had a couple of questions about Postgres 8.0 on Windows platforms:
1. Has Postgres 8.0 seen many field deployments yet? What have been
the results?
There seems to have been a good take-up. Some people will have been
deploying it even before the official release. Accu
I had a couple of questions about Postgres 8.0 on Windows platforms:
1. Has Postgres 8.0 seen many field deployments yet? What have been the results?
2. When running a test against Postgress, I noticed in the Windows task manager that several postgres.exe processes we're created. What contro
