| From: | Mel Flynn <mel(dot)flynn+pgsql(at)mailing(dot)thruhere(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | uuid_hash declaration |
| Date: | 2009-07-13 08:01:51 |
| Message-ID: | 200907130001.51246.mel.flynn+pgsql@mailing.thruhere.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
I'm trying to write a uuid extension using the FreeBSD libc uuid(3). I quickly
came to the conclusion it won't work, because:
/usr/include/uuid.h:54: error: conflicting types for 'uuid_hash'
../../src/include/utils/builtins.h:1010: error: previous declaration of
'uuid_hash' was here
Is there a way in the API to tell the backend that "uuid_hash function is
implemented by the foo__uuid_hash function" so that backwards compatibility
isn't broken?
There's 2 reasons I want this extension:
a) minimize external dependencies
b) conflict with e2fsprogs libuuid, required by my samba3 installation.
--
Mel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2009-07-13 08:16:12 | Re: Design question: Should "postgres" own all the db objects? |
| Previous Message | Johan Nel | 2009-07-13 06:54:01 | PG binary images in bytea column |