From: | "Premsun Choltanwanich" <Premsun(at)nsasia(dot)co(dot)th> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Richard Huxton" <dev(at)archonet(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: lo function changed in PostgreSQL 8.1.1 |
Date: | 2005-12-15 02:36:51 |
Message-ID: | 43A13931.C5F7.004C.0@nsasia.co.th |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thank you Tom. I will test it and reply the result as information for other. But it may a week for that cause many work in end of year.
>>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 12/14/2005 22:06:33 >>>
"Premsun Choltanwanich" <Premsun(at)nsasia(dot)co(dot)th> writes:
> I think I use contrib/lo type for manage lo. What is wrong?
You need to use the 8.1 version of contrib/lo, not any previous version.
You might find that the easiest way to manage this is to create an empty
database, load the 8.1 contrib/lo definitions by running lo.sql, then
restoring from your pg_dump backup. You'll see some complaints about
duplicate function definitions but these can be ignored.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2005-12-15 04:49:40 | Re: Which qsort is used |
Previous Message | Tom Lane | 2005-12-15 02:27:36 | Improving planning of outer joins |