On Tue, June 20, 2006 10:44 am, Tom Lane wrote:
> 78 would be ASCII 'N', but that's not really significant AFAICS. The
> problem here is that the frontend and backend have lost sync: the server is
> expecting to find a message beginning at a place in the frontend data
> stream that evidently isn't
Geoffrey <[EMAIL PROTECTED]> writes:
> ... Any subroutine that does a delete
> or update runs fine, but the subsequent routine fails with the following
> error:
> prgcaphlg: FATAL: invalid frontend message type 78
> server closed the connection unexpectedly
> This probably means the serve