pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Alexander Steinert <stony8@gmx.de>
To: pgsql-sql@postgresql.org
Subject: Re: Large Objects
Date: Thu, 28 Feb 2002 23:56:17 +0100
Message-ID: <20020228235617.A1403@tyche.svt.tu-harburg.de> (raw)
In-Reply-To: <GNELIHDDFBOCMGBFGEFOGEJDCBAA.chriskl@familyhealth.com.au>
References: <59358A738F45D51186A30008C74CE250E81448@slc-exc1.ctron.com>
<GNELIHDDFBOCMGBFGEFOGEJDCBAA.chriskl@familyhealth.com.au>
> Don't use them. They were needed when Postgres only supported 8k
> per row. Now you can just use the 'text' datatype for text data
> and the 'bytea' datatype for binary data. You have a limit of a
> few gigs per row with them.
The problem with the text or bytea type is, that inserting large amounts
of data causes a big performance loss because everything must go through
the SQL-Parser. I would be glad if someone would correct me.
So far I have found no way to grant integrity / use PG's transactions
for large objects with satisfying performance. lo_import/export for
bytea would be a very nice interface to transfer directly between the
database and files readable/writable by the client process.
Suggestions are welcome.
Stony
view thread (16+ messages) latest in thread
Message-ID: <20020228235617.A1403@tyche.svt.tu-harburg.de>
Permalink: ../20020228235617.A1403@tyche.svt.tu-harburg.de/
Also on: postgresql.org/message-id/20020228235617.A1403@tyche.svt.tu-harburg.de
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: stony8@gmx.de
Subject: Re: Large Objects
In-Reply-To: <20020228235617.A1403@tyche.svt.tu-harburg.de>
* 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