Re: pg_upgrade + Extensions

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Smitha Pamujula <smitha(dot)pamujula(at)iovation(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Grant Holly <grant(dot)holly(at)iovation(dot)com>
Subject: Re: pg_upgrade + Extensions
Date: 2015-08-31 23:28:00
Message-ID: 55E4E300.1040905@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/31/2015 07:21 PM, David E. Wheeler wrote:
> On Aug 31, 2015, at 4:20 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
>>> I think it would help if its noted somewhere in the document as it would have
>>> helped us save some time understanding why it was failing and why it was
>>> looking for json_build.
>> The problem is that this is a rare case where you had an extension that
>> was later included in Postgres.
> Maybe not so rare. Thanks to Andrew, we’ve had to do this for both 9.2-9.3 (json_object) and 9.3-9.4 (json_build).
>

Yeah, a lot of people don't like to wait for new stuff. :-)

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sumedh Pathak 2015-08-31 23:28:37 Re: Horizontal scalability/sharding
Previous Message David E. Wheeler 2015-08-31 23:21:46 Re: pg_upgrade + Extensions