pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vadivel Subramaniam <vadivel.subramaniam@flextronicssoftware.com>
To: pgsql-sql <pgsql-sql@postgresql.org>
Subject: large object support in PostGres 7.4
Date: Tue, 7 Jun 2005 11:50:16 +0530
Message-ID: <OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com> (raw)





Hi,

We have API's in /usr/local/pgsql/include/libpq-fe.h which support large
objects in PostGres
      extern int  lo_open(PGconn *conn, Oid lobjId, int mode);
      extern int  lo_close(PGconn *conn, int fd);
      extern int  lo_read(PGconn *conn, int fd, char *buf, size_t len);
      extern int  lo_write(PGconn *conn, int fd, char *buf, size_t len);
      extern int  lo_lseek(PGconn *conn, int fd, int offset, int whence);
      extern Oid  lo_creat(PGconn *conn, int mode);
      extern int  lo_tell(PGconn *conn, int fd);
      extern int  lo_unlink(PGconn *conn, Oid lobjId);
      extern Oid  lo_import(PGconn *conn, const char *filename);
      extern int  lo_export(PGconn *conn, Oid lobjId, const char
*filename);

My doubt is, do these API's operate on character data?   i.e., My table
schema is like this

table (name varchar, script varchar).  I have to store a large data(in
character form) in the script column (upto 3 MB).

As of my understanding the above mentioned API's work on the OID field.
i.e,.  table(name varchar, script oid).  Is that correct?
Please clarify this if anyone has already used this large object APIs and
specify if this has any limitation on the size?

thanks,
-Vadivel



***********************  FSS-Private   ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software Systems
Limited (FSS) and is intended solely for the use of the
individual to whom it is addressed. It may contain  privileged or
confidential information and should not be circulated or used for
any purpose other than for what it is intended. If you have received this
message in  error, please notify the originator immediately.
If you are not the intended recipient, you are notified that you are
strictly  prohibited  from  using, copying, altering, or disclosing
the contents of this message.  FSS  accepts no  responsibility  for loss or
damage arising from the use of  the information transmitted
by this email including damage from virus."




view thread (2+ messages)  latest in thread

Message-ID: <OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com>
Permalink:  ../OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com/
Also on:    postgresql.org/message-id/OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: vadivel.subramaniam@flextronicssoftware.com
  Subject: Re: large object support in PostGres 7.4
  In-Reply-To: <OF703A94D2.9C92140B-ON65257019.00220470-65257019.0022D0C7@flextronicssoftware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox