X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 769738B9E8E for ; Tue, 8 Feb 2005 01:33:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 28885-09 for ; Tue, 8 Feb 2005 01:33:03 +0000 (GMT) Received: from mail.nsasia.co.th (mail.nsasia.co.th [203.146.6.34]) by svr1.postgresql.org (Postfix) with ESMTP id 02FDE8B9CCC for ; Tue, 8 Feb 2005 01:33:04 +0000 (GMT) Received: from [192.168.200.40] (helo=jupiter.nsasia.co.th) by astaro.nsasia.co.th with esmtp (Exim 4.43) id 1CyKFT-0003KJ-B0 for pgsql-sql@postgresql.org; Tue, 08 Feb 2005 08:33:03 +0700 Received: from Thailand-MTA by jupiter.nsasia.co.th with Novell_GroupWise; Tue, 08 Feb 2005 08:32:55 +0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.3 Date: Tue, 08 Feb 2005 08:32:33 +0700 From: "Premsun Choltanwanich" To: , Subject: Re: How can I use large object on PostgreSQL Linux Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part95B6D2A1.0__=" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.204 tagged_above=0 required=5 tests=AWL, HTML_40_50, HTML_FONT_BIG, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200502/104 X-Sequence-Number: 20215 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=__Part95B6D2A1.0__= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I use SuSE only. >>> K(A*PFERL Robert 07-Feb-05 4:05 PM >>> Are you using Fedora with SELinux or just SELinux? -----Original Message----- From: Premsun Choltanwanich [mailto:Premsun@nsasia.co.th] Sent: Montag, 07. Februar 2005 05:41 To: pgsql-sql@postgresql.org Subject: [SQL] How can I use large object on PostgreSQL Linux Version? For first information, I already have Large Object that work fine on = PostgreSQL Windows Version. Now I plan to migrate all of Windows version = to Linux version. But I got some problem that make it cannot work fine = like on Windows version. =20 I found that at least Large Object that now failed and no data can be = imported to Linux version. The problem I found was shown like: ERROR: could not access file "$libdir/lo": No such file or directory ERROR: could not access file "$libdir/dbsize": No such file or directory ERROR: could not access file "$libdir/admin": No such file or directory =20 In my idea, it look like the error was related on $libdir. Maybe some = setting about $libdir is wrong but I don't know How can I check it? and = How can I correct it?? --=__Part95B6D2A1.0__= Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML I use = SuSE only.

>>> K=1B(A=D6PFERL Robert <robert.koepferl@so= norys.at> 07-Feb-05 4:05 PM >>>
Are you using Fedora with SELinux or = just SELinux?
-----Original Message-----
From: Premsun Choltanwanich = [mailto:Premsun@nsasia.co.th]
Sent: Montag, 07. Februar 2005 = 05:41
To: pgsql-sql@postgresql.org
Subject: [SQL] How = can I use large object on PostgreSQL Linux Version?

For first information, I already have Large Object = that work fine on PostgreSQL Windows Version. Now I plan to migrate all of = Windows version to Linux version. But I got some problem that make it = cannot work fine like on Windows version.
 
I found that at least Large Object that now failed and = no data can be imported to Linux version. The problem I found was = shown like:
ERROR:  could not access file "$libdir/lo": No = such file or directory
ERROR:  could not access file "$libdir/dbsize": = No such file or directory
ERROR:  could not access file "$libdir/admin": No = such file or directory
 
In my idea, it look like the error was related on = $libdir. Maybe some setting about $libdir is wrong but I don't know How = can I check it? and How can I correct it??
<= /BODY> --=__Part95B6D2A1.0__=--