> > If not, the only solution I can see is for PostgreSQL to not protest if it > > sees the > > parameter in the startup packet. > > > > Yeah, that's the ideal solution here as far as I'm concerned.
Well, it seems that's where we're ending up then. Could you prepare a patch?
