From: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres processes spending most of their time in the |
Date: | 2001-12-28 22:31:41 |
Message-ID: | Pine.LNX.4.33.0112281431120.25470-100000@windmill.gghcwest.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 28 Dec 2001, Tom Lane wrote:
> "Jeffrey W. Baker" <jwbaker(at)acm(dot)org> writes:
> > strace unfortunately doesn't deref the sembuf structure in semop.
>
> Right, but the PC would be enough to let us tell whether semop was being
> called from IpcSemaphoreLock or IpcSemaphoreUnlock.
>
> However, if the info isn't available then no use crying over it. What
> we'll need to do instead is add some debugging printouts to lwlock.c,
> and hope that the extra logfile I/O calls don't change the timing enough
> to hide the misbehavior. I'll think a little about this and send you
> an updated lwlock.c to try out.
Is there any use in frobbing these frobs?
#
# Lock Tracing
#
#trace_notify = false
#ifdef LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0
#endif
-jwb
From | Date | Subject | |
---|---|---|---|
Next Message | Nate Haggard | 2001-12-28 23:13:11 | trigger is holding up the data |
Previous Message | Tom Lane | 2001-12-28 22:26:15 | Re: postgres processes spending most of their time in the kernel |