Re: BUG #14218: pg_logical_slot_get_changes causes segmentation fault

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Alexey Kuntsevich <alexey(dot)kuntsevich(at)gmail(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14218: pg_logical_slot_get_changes causes segmentation fault
Date: 2016-06-29 17:12:10
Message-ID: CAM3SWZQGGWm25-pn=opsV8x8b1euM1uWrjkSGieXS2PXx8-4bA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 29, 2016 at 4:55 AM, Alexey Kuntsevich
<alexey(dot)kuntsevich(at)gmail(dot)com> wrote:
>
> Here is the backtrace:
>
> Reading symbols from /usr/lib/postgresql/9.5/bin/postgres...(no debugging
> symbols found)...done.

That isn't very useful, since you don't have debugging symbols. See
that Wiki page.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message andrew 2016-06-29 18:33:38 BUG #14219: rules vs. FK optimization: ERROR: no relation entry for relid 2
Previous Message Alexey Kuntsevich 2016-06-29 11:55:03 Re: BUG #14218: pg_logical_slot_get_changes causes segmentation fault