From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | eric soroos <eric-psql(at)soroos(dot)net> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Effective limit on size of text type? |
Date: | 2002-08-08 02:30:02 |
Message-ID: | 28712.1028773802@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
eric soroos <eric-psql(at)soroos(dot)net> writes:
> 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.
Given that those queries aren't using comparable WHERE conditions, I'd
wonder about the query plan myself, not the size of the returned data
item. Do you have an index on _idNum? Is it getting used?
In a quick test here, selecting a 1MB text value into a file, using
regression=# select f1 from foo
regression-# \g tmpfile
took about a tenth of a second...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | sdeel | 2002-08-08 03:52:56 | Re: Permissions problem on new install |
Previous Message | Tom Lane | 2002-08-08 02:25:05 | Re: MemoryContextAlloc: invalid request size 1969649011 |