| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oid registry |
| Date: | 2012-09-25 22:01:25 |
| Message-ID: | 506229B5.9030305@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/25/12 9:18 AM, Andrew Dunstan wrote:
> No, the difficulty (or at least the first difficulty) is in having the
> code recognize that it has an hstore at all. The code picks apart the
> record field by field at run time and takes various actions depending on
> the field's type. For any type it doesn't recognize it just outputs the
> value as a string, and so that's what it does with hstore. Mostly this
> is the right thing but in the hstore case it's rather sad.
But if you have a cast defined from hstore to json, then it is
unambiguous, because the pg_cast entry binds the types together by OID.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2012-09-25 22:06:05 | Re: Switching timeline over streaming replication |
| Previous Message | Peter Eisentraut | 2012-09-25 22:00:11 | Re: Oid registry |