| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Limiting factors of pg_largeobject |
| Date: | 2003-11-27 00:04:42 |
| Message-ID: | 3FC53F9A.5070204@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>We're still at cross-purposes then. pg_largeobject doesn't have OIDs
>(in the sense of per-row OIDs). What I thought you were complaining
>about was the chosen datatype of the LO identifier column (loid), which
>happens to be OID.
>
>
>
O.k. that was my main concern, which per your statement is unfounded ;).
If I don't have to worry about it, then that solves the issue :)
> regards, tom lane
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-11-27 01:00:59 | Re: pg_restore and create FK without verification check |
| Previous Message | Tom Lane | 2003-11-27 00:00:40 | Re: Limiting factors of pg_largeobject |