| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: intarray internals |
| Date: | 2006-05-06 20:46:15 |
| Message-ID: | 20060506204615.GF4413@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sat, May 06, 2006 at 05:38:24PM +0300, Volkan YAZICI wrote:
> > Well, it's probably trying to undo whatever g_int_compress. If you can
> > explain the algorithm used it will probably be clearer.
>
> Actually, algorithms used in the g_int_compress() and g_int_decompress()
> methods are quite awesome. (I don't know if this is the authors'
> creation, but if so, kudos.) But the problem I think is they're quite
> lossy compression methods. To clarify, here's a small explanation of
> algorithm used (if I understood right):
Well, you're right, the algorithm is quite neat. Note however that it's
only applied for integer sets with more than 100 values. I don't know
much about the intarray code, but this is a compression algorithm that
probably maps well to the domain. If you can find a lossless one that
will take 1,000 elements and can cram them into the space of 100
losslessly, we'd be glad to hear it.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | webmaster | 2006-05-06 21:57:49 | help debugging hung process |
| Previous Message | Volkan YAZICI | 2006-05-06 20:43:15 | Re: intarray internals |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-06 21:26:10 | Re: [PATCHES] [PATCH] Add support for GnuTLS |
| Previous Message | Volkan YAZICI | 2006-05-06 20:43:15 | Re: intarray internals |