| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Removing pg_migrator limitations |
| Date: | 2009-12-18 23:55:55 |
| Message-ID: | 603c8f070912181555h29174a9by719b81a391b151ce@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 18, 2009 at 6:44 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I thought there was a suggestion that we would be able to specify the oids
> in the SQL that creates the types, along the lines of:
>
> create type foo as enum ( ...) with oids ( ... );
>
> Is that a non-starter? I imagine it would need to require some special
> setting to be enabled to allow it.
This gets at a question that I've been wondering about. There seems
to be something about OIDs that makes us want to not ever allow users
to specify them, or only when our back is absolutely against the wall.
I have only the vaguest notions of what might be dangerous about
that, though.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-12-19 00:05:46 | Re: PATCH: Add hstore_to_json() |
| Previous Message | Robert Haas | 2009-12-18 23:50:25 | Re: snapshot tarball generation broken for -HEAD |