Thanks for your response.
None of the data rows are wide (as far as I can remember). We don't have
any blob data, and any text fields only contain several hundred bytes at
most (and even those would be rare).
Just stopping and starting the slon process on the slave node doesn't
seem to help
On 12/22/05, John Sidney-Woollett <[EMAIL PROTECTED]> wrote:
> In trying to investigate a possible memory issue that affects only one
> of our servers, I have been logging the process list for postgres
> related items 4 times a day for the past few days.
>
> This server uses postgres 7.4.6 + slon 1
In trying to investigate a possible memory issue that affects only one
of our servers, I have been logging the process list for postgres
related items 4 times a day for the past few days.
This server uses postgres 7.4.6 + slon 1.1.0 on Debian i686 (Linux
server2 2.6.8.1-4-686-smp) and is a slo
