| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David Parker" <dparker(at)tazznetworks(dot)com> |
| Cc: | "postgres general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_listener records |
| Date: | 2005-05-26 19:12:42 |
| Message-ID: | 4343.1117134762@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David Parker" <dparker(at)tazznetworks(dot)com> writes:
> But I'm wondering - shouldn't that be part of normal server startup,
> cleaning out the pg_listener table?
Perhaps, but the code is written such that it's unlikely to be a major
problem --- notifying processes automatically clean out entries that
don't correspond to active backend PIDs.
The long-term solution to LISTEN/NOTIFY performance issues is to get rid
of the table altogether, so I don't see a lot of point in putting effort
into band-aids like cleaning out the table during restart.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junaili Lie | 2005-05-26 19:30:51 | Archiving solution |
| Previous Message | Vivek Khera | 2005-05-26 19:08:46 | Re: Can postgresql catch all the sentences applies to one table? |