>> I have a question concerning psql. I found that psql has a defined
>> command '-t' and that it turns off printing of column names
>> and result
>> row count footers, etc.
>>
>> what I look for, is a command, which would turn off result row count
>> footer, but would print column names.
>>
> I have a question concerning psql. I found that psql has a defined
> command '-t' and that it turns off printing of column names
> and result
> row count footers, etc.
>
> what I look for, is a command, which would turn off result row count
> footer, but would print column names.
>
> is the
> I've got a problem - I need a little help. I'm using 6.5.3 from Debian
> stable.
> I've got a database, which has some fields in one table that need to hold a
> fair bit of text (say, 8000-10,000+ characters). Right now, I've got those
> fields as simple text.
[ Martin suggests breaking up the
[EMAIL PROTECTED] wrote:
> This works well for things like notes and memo's but probably not so good
> for
> huge amounts of data. Its flexible and there's no hardcoded limit to the
> length of data.
Sounds something like TOAST, part of PostgreSQL 7.1, to be released
soon. TOAST, however, is in
Believe it or not we have the same problem with DB2 on AS/400
In PG you can create large objects which is the proper answer but
there is another way...
A memo table.
This just contains a key to link up to the master record and a sequence
and a long text field, e.g. 6K.
Then write a function tha
Not sure that you can drop/create system indexes (I didn't notice that
when I posted earlier - sorry). But the the same idea may apply - can
you dump and recreate the database tables.
$ pg_dump existing > existing.dump
$ psql -e secondtry < exidting.dump
BTW, do you need to cross-post to all t
