| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: updated hstore patch |
| Date: | 2009-09-20 18:51:20 |
| Message-ID: | 612B0BCF-2239-4655-8D8B-5BD5BDFDE43E@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sep 20, 2009, at 8:43 AM, Tom Lane wrote:
>> If the perfect solution is too complex, I'd also kinda hope this
>> isn't a
>> show-stopper for this patch, but rather a TODO for the future
>> modules feature.
>
> Yeah, this is a long-standing generic issue, and not really hstore's
> problem to fix.
So then does there need to be some documentation for how to deal with
this, for those doing an in-place upgrade from an existing hstore data
type? Or would that discussion be in Bruce's tool's docs?
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-09-20 19:13:26 | Re: operator exclusion constraints [was: generalized index constraints] |
| Previous Message | David E. Wheeler | 2009-09-20 18:48:57 | Re: updated hstore patch |