Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Purusothaman A <purusothaman(dot)a(at)gmail(dot)com>
Cc: "Milen A(dot) Radev" <milen(at)radev(dot)net>, pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
Date: 2006-09-11 10:03:36
Message-ID: 20060911100336.GB16564@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

On Mon, Sep 11, 2006 at 03:27:09PM +0530, Purusothaman A wrote:
> Thanks Martijn van Oosterhout,
>
> So, I have to write my own wrapper function upon the functions below.
> 1. Oid lo_import(PGconn *conn, const char *filename);
> 2. int lo_export(PGconn *conn, Oid lobjId, const char *filename);

Not sure why you need a wrapper (you didn't say which language you were
using) but those functions work exactly like the version you put in the
SQL statements, except the filenames are for the client computer with
client permissions.

Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marco Bizzarri 2006-09-11 10:07:06 Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.
Previous Message Purusothaman A 2006-09-11 09:57:09 Re: [GENERAL] Problem with lo_export() and lo_import() from remote machine.

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-09-11 10:05:45 Re: Plan for outer joins
Previous Message Martijn van Oosterhout 2006-09-11 10:00:18 Re: Child program using parent program's transaction?