Re: Possible issue with expanded object infrastructure on Postgres 9.6.1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Workman <justin(at)photolynx(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Possible issue with expanded object infrastructure on Postgres 9.6.1
Date: 2017-08-09 03:17:04
Message-ID: 30355.1502248624@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Thu, Jan 19, 2017 at 5:45 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> A customer is on 9.6.1, and complains of a segfault observed at least
>> 3 times.
> ...
> For the sake of the archives: this now looks very much like the issue
> that Tom just fixed with commit
> 9bf4068cc321a4d44ac54089ab651a49d89bb567.

Yeah, particularly seeing that $customer noted that some of the
columns involved were UUIDs:

https://www.postgresql.org/message-id/CAOxz3fqK9Y0GntL8MDoeZjy2Ot_6Lx1YvHAY6Bd1vYkUp-iS_A@mail.gmail.com

Good to have gotten to the bottom of that one. Too bad it just
missed the train for 9.6.4.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Workman 2017-08-09 03:29:04 Re: Possible issue with expanded object infrastructure on Postgres 9.6.1
Previous Message Beena Emerson 2017-08-09 02:56:00 Re: Default Partition for Range