Re: pg_upgrade fails to detect unsupported arrays and ranges

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Subject: Re: pg_upgrade fails to detect unsupported arrays and ranges
Date: 2019-11-10 23:06:17
Message-ID: 12987.1573427177@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> Applies, builds clean and passes light testing.

Thanks for checking!

> I can see the appeal of
> including it before the wrap, even though I personally would've held off.

Nah, I'm not gonna risk it at this stage. I concur with your point
that this is an ancient bug, and one that is unlikely to bite many
people. I'll push it Wednesday or so.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2019-11-10 23:42:42 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)
Previous Message Daniel Gustafsson 2019-11-10 22:39:14 Re: pg_upgrade fails to detect unsupported arrays and ranges