From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: SUBSTRING performance for large BYTEA |
Date: | 2007-08-18 17:26:54 |
Message-ID: | 20070818172654.GB4545@merkur.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Aug 18, 2007 at 12:49:09PM -0400, Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > Should we consider setting storage external by default for the type?
>
> No. That would be counterproductive for the more typical case of bytea
> values in the range of some-small-number-of-kilobytes. Or at least
> I think that's more typical than values that are so large you have to go
> out of your way to fetch them in chunks.
Would it be feasible to add an ALTER TABLE mode
... set storage externally-extended cutoff <size> ...
where <size> is the user configurable size of the column
data at which PostgreSQL switches from extended to external
storage strategy ?
Such that large bytea values would be chunkable while
smaller ones wouldn't at the discretion of the DBA.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-08-18 17:50:16 | Re: Writing most code in Stored Procedures |
Previous Message | Joshua D. Drake | 2007-08-18 17:23:42 | Re: SUBSTRING performance for large BYTEA |