Re: BUG #14809: Heap Corruption with deeply nested triggers.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthew Maurer <matthew(dot)r(dot)maurer(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14809: Heap Corruption with deeply nested triggers.
Date: 2017-09-10 20:40:52
Message-ID: 6098.1505076052@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Matthew Maurer <matthew(dot)r(dot)maurer(at)gmail(dot)com> writes:
> In case it helps, I was running Ubuntu Xenial inside docker.

I spent some more time today trying to reproduce this, without success.
At this point it seems probably platform- or build-specific. Related
to that, the memory map you showed contains an awful lot of libraries
that I would not have expected to find loaded in a Postgres executable.
(I mean, libsqlite3? Seriously? And we don't officially support gnutls
nor libicu (in 9.6), for instance.) So my suspicion at this point is
that Ubuntu has hacked up their version of PG and broken it somehow.
You said you were running a "release build", but whose exactly?
If it's Ubuntu's, you might try the PG community build for Ubuntu
https://www.postgresql.org/download/linux/ubuntu/
or roll your own from source, and then see if you can still reproduce
the problem.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Matthew Maurer 2017-09-10 21:00:31 Re: BUG #14809: Heap Corruption with deeply nested triggers.
Previous Message Tom Lane 2017-09-10 19:02:53 Re: BUG #14808: V10-beta4, backend abort