From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Feature request - CREATE TYPE ... WITH OID = oid_number. |
Date: | 2010-12-07 15:02:53 |
Message-ID: | AANLkTikVwqDy9KS-ejJSDRd1EWVfQGYKAYjOheGLUD8j@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 7, 2010 at 9:10 AM, Dmitriy Igrishin <dmitigr(at)gmail(dot)com> wrote:
> Hey hackers@,
>
> libpq execution function works with OIDs. In some cases it is
> highly recommended specify OIDs of parameters according to
> libpq documentation.
> While developing a database application with libpq and if
> application works with custom data types IMO reasonable to
> provide developer extended type creation syntax, e.g.
> CREATE TYPE my_type ... WITH OID = 12345;
> Yes, it is possible to make dump of the database with oids,
> but if developer prefer to hard code OIDs in the application it
> would be more convenient for him to use syntax above.
> Btw, there is already Oid lo_import_with_oid function in large
> objects libpq's API which are very useful.
It's possible to do this in 9.0 in a slightly indirect way. See the
contrib/pg_upgrade folder. In particular, grep for
set_next_pg_type_oid.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-12-07 15:27:28 | Re: Spread checkpoint sync |
Previous Message | Andrew Dunstan | 2010-12-07 15:00:28 | Re: Optimize PL/Perl function argument passing [PATCH] |