Re: unexpected data beyond EOF and character encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Silvela <JSilvela(at)bear(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: unexpected data beyond EOF and character encoding
Date: 2007-03-28 15:56:41
Message-ID: 26100.1175097401@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jaime Silvela <JSilvela(at)bear(dot)com> writes:
> Wow, thanks! I'll definitely get the Unix operations guys to investigate.
> Do you know if this is tracked as an issue for Linux? I'd like some
> reassurance that whatever release Unix Ops is able to upgrade to fixes
> the bug.

I did some idle searching when we were looking at the previous report
but couldn't find any specific kernel patches about this. It's
presumably known on the kernel side but maybe not under the specific
"lseek reports stale EOF position" guise that we know it as. If you
manage to track it down please do post back here, because we'd all
like to know.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mike Charnoky 2007-03-28 15:58:21 disable/enable trigger hangs
Previous Message Stephen Harris 2007-03-28 15:48:31 Re: Slow sequential scans on one DB but not another; fragmentation?