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 /usr/lib/libefence.so.0
> > #3 0x401399ad
--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 and
> Postgres are you using? You originally posted w/ 8.1.0 but perhaps on
> the client you
On Feb 13 04:01, Andrew Klosterman wrote:
> 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").
> ...
> Program received signal SIGILL, Illegal instruction.
> [Switching to Thread 16384
"Evgeny Gridasov" <[EMAIL PROTECTED]> writes:
> autovacuum process (when active) did not respond to kill (TERM). Only kill
> -9 helped to stop autovacuum process.
autovacuum does respond to shutdown requests, but in poking at this I
found that btree index vacuuming may fail to notice a pending int
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> Alright, I have built a system with the symbols left into the binaries.
[...]
> Again, it is showing a bad malloc in what appears to be some code using
> kerberos. But there's nothing in my setup that I can think of right now
> that should induce a
* Andrew Klosterman ([EMAIL PROTECTED]) wrote:
> 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
Stephen Frost <[EMAIL PROTECTED]> writes:
> Another approach would be to have PQsetdbLogin build up a conninfo
> string and pass that into connectOptions1 instead of calling
> connectOptions1 with an empty string and then changing the values
> afterwards. That'd probably be too large of a change t
* Tom Lane ([EMAIL PROTECTED]) wrote:
> Stephen Frost <[EMAIL PROTECTED]> writes:
> > Another approach would be to have PQsetdbLogin build up a conninfo
> > string and pass that into connectOptions1 instead of calling
> > connectOptions1 with an empty string and then changing the values
> > afterwa
Andrew Klosterman <[EMAIL PROTECTED]> writes:
> (gdb) print *conn
> ...
> allow_ssl_try = 1 '\001', wait_ssl_try = 0 '\0', ssl = 0x806d1d0,
> peer = 0x807e430,
> ...
> *** glibc detected *** corrupted double-linked list: 0x0807e428 ***
Hm, it looks like the problem is associated with whatever
