Owen Hartnett <owen@clipboardinc.com> writes:
> I spent a day on this, and it's really not a PostgreSQL issue, but I
> thought I'd post it in case someone else comes down with it.
> Scenario:
> I moved the physical location and networking environment of the
> server. It's on Mac OS X - XServe, but that isn't germaine to the
> story. Originally, the server was the DHCP router for the network,
> now it sits in a demilitarized zone off a DLink router that's
> providing DHCP and NAT.
> Symptoms:
> Postgres was unable to resolve *some* simple queries, like "Select *
> from salestable where thekey = 118", although it would work for
> thekey values of 1 all the way to 117. The connection would just
> freeze, and timeout after a couple of minutes.
> My application worked this way, and so did pgAdmin, but Navicat LE didn't!
> Solution:
> I finally realized that my application and pgAdmin were both
> accessing the server using the domain name, and Navicat was using the
> IP number. Indeed, replacing the connection data with the IP number
> on the app and pgAdmin made the world safe again.
What this sounds like to me is that you've got two postmasters running
on different ports, or something close to that. The specific behavior
you describe is absolutely not sensible.
regards, tom lane