Re: [HACKERS] Speaking of pgstats

2006-04-12 Thread Bruce Momjian
Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: While we're talking about pgstats... There was some talk a while back about the whole bufferer/collector combination perhaps being unnecessary as well, and that it might be a good idea to simplify it down to just a collector. I'm

Re: [HACKERS] Speaking of pgstats

2006-04-05 Thread Tom Lane
Magnus Hagander [EMAIL PROTECTED] writes: While we're talking about pgstats... There was some talk a while back about the whole bufferer/collector combination perhaps being unnecessary as well, and that it might be a good idea to simplify it down to just a collector. I'm not 100% sure what

Re: [HACKERS] Speaking of pgstats

2006-04-05 Thread Agent M
The general idea would be to still use UDP backend-stats but get rid of the pipe part (emulated by standard tcp sockets on win32), so we'd still have the lose packets instead of blocking when falling behind. Right. Please correct me if I am wrong, but using UDP logging on the same computer

Re: [HACKERS] Speaking of pgstats

2006-04-05 Thread Tom Lane
Agent M [EMAIL PROTECTED] writes: Please correct me if I am wrong, but using UDP logging on the same computer is a red herring. Any non-blocking I/O would do, no? If the buffer is full, then the non-blocking I/O send function will fail and the message is skipped. Uh, not entirely. We'd

Re: [HACKERS] Speaking of pgstats

2006-04-05 Thread Tom Lane
Magnus Hagander [EMAIL PROTECTED] writes: While we're talking about pgstats... There was some talk a while back about the whole bufferer/collector combination perhaps being unnecessary as well, and that it might be a good idea to simplify it down to just a collector. I'm not 100% sure what