From: Michael O'Donnell <odonnellm@usgs.gov>
To: pgsql-admin-owner@postgresql.org
Cc: odonnellm@usgs.gov
Subject: checksum error messages when using md5
Date: Fri, 28 Dec 2012 07:45:03 -0700
Message-ID: <d7112f559a8e07514fd3175c4bf5a8b8@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
I am using PG 9.0 on a Windows 2008 R2 server, and I have been seeing a lot
of TCP connection errors in the log files. With Wireshark I was able to see
two things. The first was checksum errors and the second was bad TCP
connections, which I believe the latter is a result of the checksum errors.
I have a Broadcom NetXtreme 57xx Gigabit Controller, which does not permit
me to change the checksum offload configuration setting. Therefore, instead
of using md5 in the pg_hba.conf file for authentication, I am now using
password (not encrypted). When I made this change, I had no connection
errors and the speed of the jobs increased by at least 4 fold.
Would changing the NIC fix this problem or could there be a bug in the PG
Windows software? Can anyone shed light on this topic for me and how I
might best address the problem?
I am not sure why I changing the md5 to password improved performance, but
it might be simply because PG is not trying to resolve the problem. Is
there some other piece I am missing that I need to consider.
Thank you for your suggestions,
Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: odonnellm@usgs.gov, pgsql-admin-owner@postgresql.org
Subject: Re: checksum error messages when using md5
In-Reply-To: <d7112f559a8e07514fd3175c4bf5a8b8@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox