From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: thread safety on clients |
Date: | 2009-12-11 14:36:04 |
Message-ID: | 20091211143604.GC30833@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jaime Casanova wrote:
> On Thu, Dec 10, 2009 at 11:33 PM, Jaime Casanova
> <jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> > On Thu, Dec 10, 2009 at 11:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>
> >> My bet is that the real problem was a build inconsistency in
> >> the backend. Does "make distclean" and rebuild make it go away?
> >>
> >
> > actually it was a clean build just after a cvs co (not an updated
> > tree), i build the binaries and installed it in just created
> > directory...
> > i will try again now with the patch Bruce just committed
>
> the problem has gone
Yes, but what if you test with the broken pgbench? As Tom says, it
should not be able to crash the backend no matter what it does.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Smalley | 2009-12-11 14:37:44 | Re: Adding support for SE-Linux security |
Previous Message | Joshua Brindle | 2009-12-11 14:34:32 | Re: Adding support for SE-Linux security |