From: | Dana Hudes <dhudes(at)tcp-ip(dot)info> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Dana Hudes <dhudes(at)tcp-ip(dot)info>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: bytea or blobs? |
Date: | 2004-02-18 15:17:39 |
Message-ID: | Pine.LNX.4.58.0402181015520.729@screamer.tcp-ip.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
How can one measure the result of the compression -- can I see this in
some table or with some pgsql command?
At what threshold does it take place, I think its 8192?
The nasty bit is not one picture of 100kb.
Its 20 pictures of 5kb.
On Wed, 18 Feb 2004, Richard Huxton wrote:
> On Wednesday 18 February 2004 06:44, Dana Hudes wrote:
> >
> > At least with base64 I have ample libraries and can convert my data
> > before sending to sql or after receiving from sql. It becomes my
> > application's issue. Mind, this bloats the data considerably.
> > escape is less bloat but I have to recreate the encode/decode in my app,
> > so far as I see.
>
> Less bloat than you might expect - large values are TOASTed and compressed.
> I'm guessing a lot of your redundancy will be eliminated.
>
> Having said that, bytea's purpose in life is to store your binary data.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-18 15:21:31 | Re: Indexes and statistics |
Previous Message | Richard Huxton | 2004-02-18 09:44:42 | Re: bytea or blobs? |