From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: fix log_min_duration_statement logic error |
Date: | 2003-10-05 16:20:52 |
Message-ID: | 1024.1065370852@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Peter, any problems with pid wrap-around? I am thinking we need to
> prepend a "wrap count" on the front of the pid output for 7.5.
Why? And how would you know when the PIDs have wrapped anyway?
The OS already guarantees that no two concurrently running procs have
the same PID. That seems sufficient to me. It's conceivable that a PID
could be recycled quickly enough that it wasn't obvious from the logs
that this was a new backend process and not the same old one, but do you
care? (And if you did care, wouldn't you be monitoring log_connections,
which would tip you off?)
I think this is a red herring.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-10-05 16:34:18 | Re: fix log_min_duration_statement logic error |
Previous Message | Tom Lane | 2003-10-05 16:17:48 | Re: fix log_min_duration_statement logic error |