"Eric Nielsen" <ericnielsen@earthlink.net> writes:
> About 2/3 of the way through, one
> of the tables (which one depends on the amount of debugging echo's in the
> code) gets corrupted and a row is truncated, causing the next row to start
> within a preceding row. The variable containing the row to print is correct
> and will print to a file correctly. Somewhere between the php echo
> statement and the browser the line gets truncated. The line is no longer or
> shorter than the other lines around it that made it through fine.
> The code works on an apache server running on a machine with 128 MB ram (the
> AOLServer machine has 64 MB ram). The page itself is about 80Kb because of
> all the hidden fields in the forms.
Hm. Does the truncation happen to occur near the 64Kb mark in the page
contents? If so, that'd suggest buffer overrun somewhere in PHP (since
64K would be a pretty likely choice for a buffer size).
> I know this is outside the scope of this list,
Yeah, I'm afraid this is pretty far off-topic for Postgres. I suggest
going back to rag on the PHP people some more. I rather suspect that
you'll find the problem is reproducible without Postgres, if you just
make up a script that echoes the same total volume of data...
regards, tom lane