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

Thanks for spending time trying to reproduce it. I am using the build
from the apt repository

deb http://apt.postgresql.org/pub/repos/apt/ xenial-pgdg main

postgresql-9.6 9.6.5-1.pgdg16.04+1

I chased down the depencency chain to find out why libsqlite3 is
present. It is linked against libldap, which is in turn linked against
libgssapi, which is in turn linked against libheimntlm, which is in
turn linked to libkrb5, which is then linked to libsqlite3.

I can chase down the other dependencies if you'd like, but I expect
that those are in the process for similar reasons.

On Sun, Sep 10, 2017 at 4:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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