| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | akavan(at)cox(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Stats Collector Error 7.4beta1 and 7.4beta2 |
| Date: | 2003-09-04 05:32:40 |
| Message-ID: | 1062653560.9242.28.camel@zeutrh9 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2003-09-04 at 01:23, Tom Lane wrote:
> Hm. Could it be an IPv6 issue --- that is, the stats collector is alive
> and faithfully listening on some UDP port, but it's not the same port
> the backends try to send to? Given the discussion over the past couple
> of days about bizarre interpretations of loopback addresses in
> pg_hba.conf, I could sure believe there's some similar kind of issue for
> the stats collector.
I had a similar thought, but I have no idea how I would verify this.
The thing is, when I recompiled postgresql myself, I left pg_hba.conf at
default settings, and it's running on RH9, which I am running and have
not had a problem with...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-04 05:32:54 | Re: Stats Collector Error 7.4beta1 and 7.4beta2 |
| Previous Message | Bruce Momjian | 2003-09-04 05:31:44 | Problem with pg_attribute.attstorage for pg_class.relacl |