Joe Kislo <postgre(at)athenium(dot)com> writes:
> Hmm, 1G is probably fine :) But is there going to be a blob type with
> toast? If I want to store a large binary object, and have the ability
> of retrieving it strictly over the postgre database connection, would I
> be retrieving a blob column, or a really long varchar column?
If you want binary (8-bit-clean) data, you need to use the 'bytea'
datatype not 'varchar'. Our character datatypes don't cope with
embedded nulls presently. This is primarily an issue of the
external representation as a C string.
Alternatively, you can keep using the old-style large-object support
(lo_read, lo_write, etc). This may be handy if you are dealing with
blobs large enough that you don't want to read or write the entire
value on every access. We need to add that capability to bytea too,
by defining some access functions that allow reading and writing
portions of a bytea value --- but no one's gotten round to that yet,
so I don't suppose it'll happen for 7.1.
regards, tom lane
In response to
pgsql-general by date
|Next:||From: Wojciech Milek||Date: 2000-11-30 18:16:02|
|Subject: RE: [SQL] a script that queries database periodically|
|Previous:||From: Hancock, David (DHANCOCK)||Date: 2000-11-30 17:57:09|
|Subject: RE: Help with Database Recovery|