| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-05 14:53:41 |
| Message-ID: | 53173A75.4080601@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/05/2014 09:39 AM, Bruce Momjian wrote:
>
> So, I am going to ask a back-track question and ask why we can't move
> hstore into core. Is this a problem with the oids of the hstore data
> type and functions? Is this a pg_upgrade-only problem? Can this be
> fixed?
Yes, pg_upgrade is the problem, and no, I can't see how it can be fixed.
Builtin types have Oids in a certain range. Non-builtin types have Oids
outside that range. If you have a clever way to get over that I'd be all
ears, but it seems to me insurmountable right now.
A year or two ago I made a suggestion to help avoid such problems in
future, but as Josh said it got shot down, and in any case it would not
have helped with existing types such as hstore.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-03-05 14:58:47 | Re: Review: Patch FORCE_NULL option for copy COPY in CSV mode |
| Previous Message | Craig Ringer | 2014-03-05 14:44:00 | Re: Row-security on updatable s.b. views |