From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Postgres Question <postgresquestion(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: UDP Overflow / UDP Drops on Standby Postgres Service |
Date: | 2014-01-21 18:22:34 |
Message-ID: | 31369.1390328554@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Postgres Question <postgresquestion(at)gmail(dot)com> writes:
> Essentially a UDP buffer associated with the pg_standby process on my
> localhost interface gradually fills up once I start Postgres until it
> hits its maximum capacity and then proceeds to steadily drop packets. A
> restart of Postgres (of course) clears the buffer, but then it begins
> filling up again.
AFAICS, there is nothing at all in pg_standby that does IPC of any sort,
let alone UDP transmission in particular. It just does filesystem
access. Perhaps you're running on an NFS filesystem and the UDP traffic
is associated with that? If so, though, any failure to collect packets
would be a bug in glibc, not pg_standby.
A different theory is that pg_standby is just the last surviving child
of some process that opened a UDP port and never closed it. What is
spawning pg_standby in your system?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-01-21 18:39:13 | Re: pg_upgrade fails: "Mismatch of relation OID in database" - 9.2.4 to 9.3.2 |
Previous Message | Tom Lane | 2014-01-21 17:21:44 | Re: client_min_messages not suppressing messages in psql nor pgAdminIII |