--- Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> This is a known problem on WIndows. THe stats
> processor sometimes falls
> down under heavly load. And if you enable
> row-level-stats the load goes
> up considerably - especially during bulk inserts.
>
> //Magnus
>
Well then I guess I'll be
> I'm having an issue with what appears to be the stats
> collector process dying on Postgresql 8.0.1 running on
> Windows XP w/sp1.
>
> I've enabled
> stats_command_string and stats_row_level in my config file.
> During bulk inserts the stats collector process appears to
> encounter some sor
Shelby Cain <[EMAIL PROTECTED]> writes:
> I'm having an issue with what appears to be the stats
> collector process dying on Postgresql 8.0.1 running on
> Windows XP w/sp1.
> 2005-02-23 14:59:17 FATAL: could not read from statistics collector pipe: No
> such file or directory
> 2005-02-23 14:59:
--- "Matthew T. O'Connor" wrote:
> Windows firewall perhaps?
>
I double checked to make sure it was disabled.
Regardless, if a firewall were preventing the
connection from occuring I'm fairly certain the error
would be something other than "target machine actively
refused" which implies tryin
Windows firewall perhaps?
Shelby Cain wrote:
I'm having an issue with what appears to be the stats
collector process dying on Postgresql 8.0.1 running on
Windows XP w/sp1.
I've enabled
stats_command_string and stats_row_level in my config
file. During bulk inserts the stats collector process
appe
I'm having an issue with what appears to be the stats
collector process dying on Postgresql 8.0.1 running on
Windows XP w/sp1.
I've enabled
stats_command_string and stats_row_level in my config
file. During bulk inserts the stats collector process
appears to encounter some sort of problem and sh
