On Thu, 2007-01-04 at 13:17 -0500, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > Wouldn't it be better to issue ReadyForQuery() and then issue the stat
> > stuff in the gap between processing?
>
> To me, "ready for query" means "ready for query", not "I think I might
> be ready
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Wouldn't it be better to issue ReadyForQuery() and then issue the stat
> stuff in the gap between processing?
To me, "ready for query" means "ready for query", not "I think I might
be ready soon". Otherwise you could argue for trying to move the
messag
In postgres.c main loop, I note that we issue ReadyForQuery() *after*
updating pgstat and setting the ps display.
Wouldn't it be better to issue ReadyForQuery() and then issue the stat
stuff in the gap between processing?
That way we would be less likely to care about pgstat and the ps,
potenti
