hi jerry,
try killing mDNSResponder before restarting postgres:
sudo killall mDNSResponder
hopefully apple fixes this dns-problems in 10.6.1.
regards, jan otto
The rascal gets respawned immediately ;(
Of course it will be respawned, but all the cache is disposed (the
broken entries too) and
you should be able to start postgres. it has nothing to do with
postgres itself, other programs
and tools that using dns lookups affected too.
regards, jan otto
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
