Horton

Re: [GENERAL] pg_upgrade problem

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: depesz@depesz.com
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 2011-09-05T18:51:12Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. ltree support for multibyte encodings. Patch was made by

hubert depesz lubaczewski wrote:
> On Mon, Sep 05, 2011 at 02:18:18PM -0400, Bruce Momjian wrote:
> > hubert depesz lubaczewski wrote:
> > > I'm not sure if it's upgrade thing, or is it because of error in
> > > ltree/compilation, but it looks bad.
> > > 
> > > Is there any more info I could show/gather to help debug the issue?
> > 
> > I am confused by the error --- is it not loading, or can you get a
> > backtrace of the crash?
> 
> The one in logs is not sufficient?
> If not - could you tell me how to make the backtrace? I'm by far not a c
> programmer, so for this I'd need some tutoring.

I think you want this:

	http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD

While strace is useful, it doesn't show us where the C code is failing.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +