Bob Smith <[EMAIL PROTECTED]> writes: > PostgreSQL 7.0.2 Time to update ...
I'm rather surprised that restarting the postmaster didn't make the
error go away, but it's unlikely that anyone will care to investigate
--- unless you can reproduce the problem in 7.1.3 or later.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
