| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, Maciej Gajewski <maciej(dot)gajewski0(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unsigned integer types |
| Date: | 2013-05-28 23:16:20 |
| Message-ID: | 51A53AC4.2030305@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/28/2013 07:00 PM, Bruce Momjian wrote:
> On Tue, May 28, 2013 at 05:57:41PM -0500, Jim Nasby wrote:
>>>
>>> Did you try 'oid' as an unsigned int4?
>> Using an internal catalog type for user data seems like a horrible idea to me...
> Uh, not sure if we can say oid is only an internal catalog type. It is
> certainly used for storing large object references.
>
pg_largeobject has oids. I don't thing the fact that we use oids to
store references to pg_largeobject should blind us to the fact that oid
should be an opaque type. Using them as substitute unsigned ints seems
like a horrible idea to me too.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-05-28 23:22:42 | Re: getting rid of freezing |
| Previous Message | Bruce Momjian | 2013-05-28 23:05:07 | Re: Planning incompatibilities for Postgres 10.0 |