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
#trace_locks = false
#trace_userlocks = false
#trace_lwlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0
In response to
pgsql-general by date
|Next:||From: Nate Haggard||Date: 2001-12-28 23:13:11|
|Subject: trigger is holding up the data|
|Previous:||From: Tom Lane||Date: 2001-12-28 22:26:15|
|Subject: Re: postgres processes spending most of their time in the kernel |