| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oid registry |
| Date: | 2012-09-25 01:37:11 |
| Message-ID: | 1348537031.18490.5.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2012-09-24 at 18:59 -0400, Andrew Dunstan wrote:
> This rather overdue mail arises out the developer's meeting back in
> May, where we discussed an item I raised suggesting an Oid registry.
>
> The idea came from some difficulties I encountered when I did the
> backport of the JSON work we did in 9.2 to 9.1, but has wider
> application. Say someone writes an extension that defines type A. You
> want to write an extension that takes advantage of that type, but it's
> difficult if you don't know the type's Oid,
Could you fill the rest of us in with some technical details about why
this might be necessary and what it aims to achieve?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-09-25 01:43:20 | plpgsql gram.y make rule |
| Previous Message | Tom Lane | 2012-09-25 01:24:05 | Re: Oid registry |