On Sat, Aug 27, 2011 at 3:30 PM, Tom Lane wrote:
> Daniel Farina writes:
>> On Sat, Aug 27, 2011 at 1:51 PM, Tom Lane wrote:
>>> A more long-range point about it is that the next time we make a
>>> protocol version bump that affects the format of error messages,
>>> the problem comes right back.
Daniel Farina writes:
> On Sat, Aug 27, 2011 at 1:51 PM, Tom Lane wrote:
>> A more long-range point about it is that the next time we make a
>> protocol version bump that affects the format of error messages,
>> the problem comes right back. It'd be better if the message somehow
>> indicated tha
On Sat, Aug 27, 2011 at 1:51 PM, Tom Lane wrote:
> A more long-range point about it is that the next time we make a
> protocol version bump that affects the format of error messages,
> the problem comes right back. It'd be better if the message somehow
> indicated that the server hadn't made any
I wrote:
> Magnus Hagander writes:
>> On Sat, Aug 27, 2011 at 01:59, Tom Lane wrote:
>>> Now, seeing as how NEGOTIATE_SSL_CODE has been understood by every build
>>> since PG 7.0, I believe that this is dead code and we could remove it;
>>> it seems exceedingly unlikely that any modern build of l
I wrote:
> Lastly, I noticed that if I tried this repeatedly on a Unix socket,
> I sometimes got
> psql: server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> could not send startup packet: Broke
Magnus Hagander writes:
> On Sat, Aug 27, 2011 at 01:59, Tom Lane wrote:
>> Now, seeing as how NEGOTIATE_SSL_CODE has been understood by every build
>> since PG 7.0, I believe that this is dead code and we could remove it;
>> it seems exceedingly unlikely that any modern build of libpq will ever
On Sat, Aug 27, 2011 at 01:59, Tom Lane wrote:
> Daniel Farina writes:
>> Some Postgres servers will error out for a while with the following
>> error message:
>> "expected authentication request from server, but received c"
>> [ and this seems to be triggered by fork failures in the server ]
>
>
Daniel Farina writes:
> Some Postgres servers will error out for a while with the following
> error message:
> "expected authentication request from server, but received c"
> [ and this seems to be triggered by fork failures in the server ]
Fascinating.
I poked at this for awhile by the expedien
Hello list,
This is something that I've only recently somewhat pinned down to a cause...
Some Postgres servers will error out for a while with the following
error message:
"expected authentication request from server, but received c"
If one uses Their Favorite Search Engine, this message is sca
