On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > I threw in a pthread mutex around the code making the database connections
> > for each of my threads. The problem is still there ("corrupted
> > double-linked list"
On Mon, 13 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /usr/lib/lib
On Wed, 8 Feb 2006, Tom Lane wrote:
> "Andy Klosterman" <[EMAIL PROTECTED]> writes:
> > SPECULATION: Another possibility is that I misunderstand some aspect of
> > multi-threaded interactions with Postgres (I open uniquely named connections
> > to the DB for each thread of my test program). Maybe
On Mon, 13 Feb 2006, Stephen Frost wrote:
> * Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> > (gdb) bt
> > #0 0x401c3851 in kill () from /lib/libc.so.6
> > #1 0x40139dd5 in EF_Abort () from /usr/lib/libefence.so.0
> > #2 0x40139823 in memalign () from /us
On Tue, 14 Feb 2006, Jens-Wolfhard Schicke wrote:
> --On Montag, Februar 13, 2006 21:25:30 -0500 Stephen Frost
> <[EMAIL PROTECTED]> wrote:
>
> > * Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> >> > Seems kind of unlikely... What exact (.deb) versions of libpq
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> > We may be spending too much time on this one point --- as long as
> > Kerberos isn't *writing* into the zero-length alloc, there is nothing
> > illegal immoral or fattening about malloc(0). Can you get ElectricFence
>
On Tue, 14 Feb 2006, Andrew Klosterman wrote:
> On Mon, 13 Feb 2006, Stephen Frost wrote:
>
> > Hmm, alright, well, this is at least not the fault of the patch of mine
> > which was included in Debian's 8.1.2-2 Postgres release. :) You might
> > try compiling som
On Tue, 14 Feb 2006, Stephen Frost wrote:
> It's kind of a chicken-and-egg here because the backend decides what
> authentication mechanism to ask for based off the username (at least in
> part) through pg_hba.conf, so you can't find out the authentication
> method until you know the username so a
> We may be spending too much time on this one point --- as long as
> Kerberos isn't *writing* into the zero-length alloc, there is nothing
> illegal immoral or fattening about malloc(0). Can you get ElectricFence
> to not abort right here but continue on to the real problem?
>
>
> > Tracking down exactly what's tickling the problem in this case could be
> > tricky...
>
> Yeah :-(. If you aren't able to narrow it further by yourself, please
> try to put together a self-contained test case.
>
> regards, tom lane
Well, my attempt last night at putting
On Mon, 13 Feb 2006, Stephen Frost wrote:
> Hmm, alright, well, this is at least not the fault of the patch of mine
> which was included in Debian's 8.1.2-2 Postgres release. :) You might
> try compiling some debs with debugging enabled. This is (reasonably)
> straight-forward:
>
> (as root:)
>
On Wed, 15 Feb 2006, Tom Lane wrote:
> Andrew Klosterman <[EMAIL PROTECTED]> writes:
> > With the debug binaries, I was able to step through the program and get to
> > what appears to be the function where it bails: line 1166 of
> > postgresql-8.1.0/src/interfa
12 matches
Mail list logo
