From: | eric soroos <eric-psql(at)soroos(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, eric soroos <eric-psql(at)soroos(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SMP-PPC spinlocks in 7.2.4? |
Date: | 2003-03-11 22:10:39 |
Message-ID: | 859131.1164730657@[4.42.179.151] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom,
> Hm. Do they use query-cancels at all? The reference to async_notify
> makes me wonder if this is related to the recently-discovered
> async_notify bug that could prevent fast-mode shutdowns. I'm not
> certain how that might lead to an apparent deadlock, but a query cancel
> arriving during async_notify would surely improve the odds of trouble.
Not that I know of, unless it's for cleanup of queries when quitting the app or other such abort type states.
> If you don't mind running a slightly customized version, you might try
> back-patching this fix:
> http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/commands/async.c.diff?r1=1.91&r2=1.91.2.1
> into 7.2.4 and see if that improves matters.
I'll give that a shot.
> If it doesn't, I'd be interested to look into the matter, but I'd
> probably need access to the machine to see what is going on.
That's probably possible, but there are some client confidentiality issues.
> > Is there anything I can do to debug this? I'm willing to give it a
> > shot, but I'm also rapidly preparing a single proc linux/intel machine
> > to take over db duties.
>
> I think you're mistaken to be blaming the hardware...
The linux box is a migration that's being accelerated from this issue. It has more drive, more memory, no app servers, and control of the kernel shared memory parameters.
eric
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Hatcher | 2003-03-11 22:31:36 | is there a way to sets DBI char encoding? |
Previous Message | Tom Lane | 2003-03-11 21:46:23 | Re: SMP-PPC spinlocks in 7.2.4? |