[ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-06 Thread Alanoly Andrews
Hello, OS level = AIX 5.3 ML-8 Postgres version = 9.0 beta-4 I'm testing "hot standby" using "streaming WAL records". On trying to bring up the hot standby, I see the following error in the log: LOG: database system was interrupted; last known up at 2010-08-05 14:46:36 EDT LOG: entering stan

Re: [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-06 Thread Fujii Masao
On Fri, Aug 6, 2010 at 10:10 PM, Alanoly Andrews wrote: > I’m testing “hot standby” using “streaming WAL records”. On trying to bring > up the hot standby, I see the following error in the log: Thanks for the report! > LOG:  database system was interrupted; last known up at 2010-08-05 14:46:36 >

Re: [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-06 Thread Alanoly Andrews
: [ADMIN] postgres 9.0 crash when bringing up hot standby On Fri, Aug 6, 2010 at 10:10 PM, Alanoly Andrews wrote: > I'm testing "hot standby" using "streaming WAL records". On trying to bring > up the hot standby, I see the following error in the log: Thanks fo

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-06 Thread Heikki Linnakangas
On 06/08/10 17:31, Fujii Masao wrote: On Fri, Aug 6, 2010 at 10:10 PM, Alanoly Andrews wrote: I’m testing “hot standby” using “streaming WAL records”. On trying to bring (dbx) where _alloc_initial_pthread(??) at 0x949567c __pth_init(??) at 0x9493ba4 uload(??, ??, ??, ??, ??, ??,

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-11 Thread Robert Haas
On Fri, Aug 6, 2010 at 3:53 PM, Heikki Linnakangas wrote: > So, loading libpqwalreceiver library crashes. It looks like it might be > pthread-related. Perhaps something wrong with our makefiles, causing > libpqwalreceiver to be built with wrong flags? Does contrib/dblink work? If > you look at the

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-11 Thread Robert Haas
On Wed, Aug 11, 2010 at 10:20 AM, Alanoly Andrews wrote: > Ok..in response to the questions from Heikki, > > 1. Yes, "contrib/dblink" does work. Here's the output from the command used > to "make" dblink: >      postgres:thimar> /usr/bin/gmake -C contrib/dblink install >      gmake: Entering dire

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-11 Thread Alanoly Andrews
il.com] Sent: Wednesday, August 11, 2010 10:13 AM To: Heikki Linnakangas Cc: Alanoly Andrews; pgsql-admin@postgresql.org; PostgreSQL-development Subject: Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby On Fri, Aug 6, 2010 at 3:53 PM, Heikki Linnakangas wrote: > So

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-12 Thread Robert Haas
On Wed, Aug 11, 2010 at 10:25 AM, Robert Haas wrote: > [request form more information] Per off-list discussion with Alanoly, we've determined the following: dblink was compiled with the same flags as libpqwalreciever dblink works libpqwalreceiver crashes -- Robert Haas EnterpriseDB: http://www

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-12 Thread Tom Lane
Robert Haas writes: > Per off-list discussion with Alanoly, we've determined the following: > dblink was compiled with the same flags as libpqwalreciever > dblink works > libpqwalreceiver crashes I wonder if the problem is not so much libpqwalreceiver as the walreceiver process. Maybe an ordina

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-12 Thread Tom Lane
I wrote: > I wonder if the problem is not so much libpqwalreceiver as the > walreceiver process. Maybe an ordinary backend process does some > prerequisite initialization that walreceiver is missing. Hard to > guess what, though ... I can't think of anything dlopen() depends on > that should be u

Re: [HACKERS] [ADMIN] postgres 9.0 crash when bringing up hot standby

2010-08-13 Thread Robert Haas
On Thu, Aug 12, 2010 at 5:54 PM, Tom Lane wrote: > I wrote: >> I wonder if the problem is not so much libpqwalreceiver as the >> walreceiver process.  Maybe an ordinary backend process does some >> prerequisite initialization that walreceiver is missing.  Hard to >> guess what, though ... I can't