From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | andremachado(at)techforce(dot)com(dot)br, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: large objects and pg 7.3.x |
Date: | 2003-08-19 04:02:57 |
Message-ID: | 3F41A171.5486A3FC@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Tom Lane wrote:
>
> Andre Felipe Machado <andremachado(at)techforce(dot)com(dot)br> writes:
> > Since pg 7.3.0, the prescribed workaround to create a new type "lo" does not
> > work anymore.
>
> I think this is just a matter of obsolete documentation ---
Maybe pointing to contrib/lo is preferable. However, few people
take care of contrib/lo and it seems easily broken.
PostgreSQL has never supported LO properly and I can't recommend
anything for continuous LO use.
> if you can
> point to where it still says to use a CREATE TYPE hack, we can fix it.
> The easy way to define "lo" now is just as a domain over oid:
> CREATE DOMAIN lo AS oid;
I'm suspicious if it still works even in 7.4.
Can we find the oid of the domain "lo" in the row description
message from the backend ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-19 04:08:18 | Re: large objects and pg 7.3.x |
Previous Message | Tom Lane | 2003-08-19 01:22:42 | Re: large objects and pg 7.3.x |