Tom Lane wrote:
> Perhaps an appropriate thing to do is separate out the representation
> change from the other new features, and apply just the latter for now.
> Or maybe we should think about having two versions of hstore.  This
> is all tied up in the problem of having a decent module infrastructure
> (which I hope somebody is working on for 8.5).  I don't know where
> we're going to end up for 8.5, but I'm disinclined to let a fairly
> minor contrib feature improvement break upgrade-compatibility before
> we've even really started the cycle.

I can just have pg_migrator detect hstore and require it be removed
before upgrading;  we did that already for 8.3 to 8.4 and I am assuming
we will continue to have cases there pg_migrator just will not work.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

• Re: revised hstore patch at 2009-07-21 23:25:52 from Tom Lane

Responses

• Re: revised hstore patch at 2009-08-09 12:23:39 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2009-08-09 00:53:55
	Subject: a short trip in the wayback machine
Previous:	From: Mark Kirkwood	Date: 2009-08-09 00:47:18
	Subject: Re: Lock Wait Statistics (next commitfest)