From: | vishal saberwal <vishalsaberwal(at)gmail(dot)com> |
---|---|
To: | lolke(dot)dijkstra(at)chello(dot)nl |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: BLOB and OID |
Date: | 2005-11-04 19:27:51 |
Message-ID: | 3e74dc250511041127y4f69c0a1w86c2023a13c8f213@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
yes, there is one, but i dont know how would you modify the PostgreSQL code.
You can implement a GUID datatype and can use it as indexing which
guarantees uniqueness and can be stored in double format.
thanks,
vish
On 11/4/05, Lolke B. Dijkstra <lolke(dot)dijkstra(at)chello(dot)nl> wrote:
>
> Hi,
>
> OID being a 4 byte int seems limited to indexing for binary objects.
> More precisely I use BLOB to store images in the database and link these
> objects to another table using the OID as FK.
> If I run out of OID there will be no way to index new images. Of course
> when not automatically creating OID for all objects in the database you
> will not easily run out of index values, but still..
> Is there an alternative way of indexing BLOB? Or can I extend the range
> of OID?
>
> Lolke
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-04 19:52:10 | Re: pl/pgsql list as parameter. |
Previous Message | vishal saberwal | 2005-11-04 19:25:46 | Re: Image File System Question |