Re: revised hstore patch

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: revised hstore patch
Date: 2009-08-09 12:23:39
Message-ID: 4A7EBFCB.1040105@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> 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.
>
>

The more things you exclude the less useful the tool will be. I'm
already fairly sure it will be unusable for all or almost all my clients
who use 8.3.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-08-09 13:53:39 Re: revised hstore patch
Previous Message James Mansion 2009-08-09 11:09:26 Re: slow commits with heavy temp table usage in 8.4.0