Re: Parallel safety of binary_upgrade_create_empty_extension

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel safety of binary_upgrade_create_empty_extension
Date: 2018-03-27 02:39:02
Message-ID: CAEepm=0i46hh4N9h68rXcb99D17ArSibcZqWVzxmYE2gOq+b=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 27, 2018 at 3:30 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> I hacked something up in Python

# otool -tvV | \

In case anyone is interested in trying that, it should be "otool -tvV
[path to postgres executable compiled with -O0]" (meaning disassemble
it). I was removing my home directory from the path before sending
and apparently got carried away...

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Edmund Horner 2018-03-27 02:47:07 Fix for pg_stat_activity putting client hostaddr into appname field
Previous Message Thomas Munro 2018-03-27 02:30:21 Re: Parallel safety of binary_upgrade_create_empty_extension