From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Tareq Aljabban <dee(dot)jay23(dot)me(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Storage Manager crash at mdwrite() |
Date: | 2012-03-16 23:29:58 |
Message-ID: | 1331940598.5271.132.camel@sussancws0025 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2012-03-16 at 18:02 -0400, Tareq Aljabban wrote:
> Thanks for your response Jeff..
> It's true that libhdfs code resides under the c++ folder, but in all
> of the documentation, libhdfs is referred to as the C interface of
> HDFS.
> Now what you're saying makes sense.. that nothing guarantees this will
> work well.. but in the phase of initDB, the function calls are done
> nicely without any exceptions.. when starting the postmaster,
> something wrong happens after 3 calls to libhdfs.. that's what I'm
> confused about..
> What it's the difference between the two processes (initDB, start
> postmaster), that might cause this crash to happen?
There is a lot of difference between those two. In particular, it looks
like the problem you are seeing is coming from the background writer,
which is not running during initdb.
I think the next step would be for you to compile in debug mode with
-O0, and attach to the bgwriter process with gdb, and step through it.
Then, you can see the exact path which causes the bgwriter to exit, and
that will give you a better idea where the problem is.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-03-16 23:42:07 | Re: pg_terminate_backend for same-role |
Previous Message | Alvaro Herrera | 2012-03-16 23:11:17 | Re: pg_upgrade and pg_config dependency |