From: | eric soroos <eric-psql(at)soroos(dot)net> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Effective limit on size of text type? |
Date: | 2002-08-07 18:45:35 |
Message-ID: | 10848145.1183401761@[4.42.179.151] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Using pg 7.2.1 on OsX 10.1.5
I'm trying dumping encoded email attachments into a text field. Inserts complete quickly enough that I don't notice a performance hit (~1 sec).
However,
test=# \x
test=# select _incomingEnclosures from dl_event where _idNum=3010;
Takes at least a couple of minutes, either through psql or a libpq based connection.
test=# select char_length(_incomingEnclosures) from dl_event where _donorNum=804 and _responseNum=3010;
-[ RECORD 1 ]-------
char_length | 952478
Is nearly immediate.
Then again, without the \x view, I get the header of the column almost instantly, and the rest does scroll by my console. (perhaps cached?)
Is this an issue with the frontend or the backend? Can I work around this by using a different data type? (I'm not sure that large objects are well supported in my client library) Maybe bina?
eric
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Corey | 2002-08-07 21:06:49 | Re: Database Structure |
Previous Message | Thilo Hille | 2002-08-07 17:25:18 | MemoryContextAlloc: invalid request size 1969649011 |