On Fri, Nov 16, 2007 at 06:31:43AM +0100, Christian Ullrich wrote:
> * Magnus Hagander wrote:
> >Christian Ullrich wrote:
> >>psql tells me about an "invalid frontend message type 112". Most of the
> >>time, that error comes as the first line of output from psql (above the
> >>"Welcome to" line), sometimes it is displayed later:
> >Does it work if you run the client on the same machine as the server?
> >How's your AD set up - single domain, or multiple?
> Single domain, AD native mode, DC is Windows 2000.
> >Do you get anything in the server logs (please check both eventlog and
> >the pg_log directory)
> Nothing relevant in eventlog, and pg_log only has the "invalid frontend
> message type 112" lines. Interspersed with "loaded library
> $libdir/plugin_debugger.dll", but I guess that's not important here.
> >And yes, please send me a network trace off-list. (send the rest of the
> >responses on-list in case someone else has a good idea :-P)
> Attached. Starting with frame 15 I ran "\d".
I have applied a patch for this to HEAD that fixes the problem (confirmed
off-list with Christian).
Before someone asks, there's a similar codepath in the GSSAPI code, but it
already contains the check ;-)
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2007-12-04 15:32:09|
|Subject: Re: BUG #3790: pg_restore error canceling statement due touser request |
|Previous:||From: Stefan Kaltenbrunner||Date: 2007-12-04 12:04:41|
|Subject: Re: BUG #3798: Add fuzzy string search in TSearch2|