Re: Oid registry

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oid registry
Date: 2012-09-26 14:38:23
Message-ID: 5063135F.6030506@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/25/12 8:48 PM, Andrew Dunstan wrote:
> That still leaves the other uses for having well known Oids (or possibly
> UUIDs) for non-builtin types (e.g. so Drivers don't have to look them up
> in the catalogs, or having issues when types are added to the core.)

Here is a problem: If I write an "hstore-ng" extension, I have two options:

1. "Steal" the OID/UUID assigned to hstore so my extension integrates
nicely with all the drivers.

2. Don't steal the OID/UUID assigned to hstore and have a very low
chance that my extension will ever be supported nicely by a lot of drivers.

Neither option is very nice.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2012-09-26 14:47:01 Re: autovacuum stress-testing our system
Previous Message Dimitri Fontaine 2012-09-26 14:36:38 Re: [9.1] 2 bugs with extensions