On Mon, Jan 3, 2011 at 4:02 AM, Jim Nasby wrote:
> FWIW, last time I looked at how Oracle handled compression, it would only
> compress existing data. As soon as you modified a row, it ended up
> un-compressed, presumably in a different page that was also un-compressed.
IIUC, InnoDB basically c
On Jan 2, 2011, at 5:36 PM, Simon Riggs wrote:
> On Tue, 2010-12-28 at 09:10 -0600, Andy Colson wrote:
>
>> I know its been discussed before, and one big problem is license and
>> patent problems.
>
> Would like to see a design for that. There's a few different ways we
> might want to do that, a
On Tue, 2010-12-28 at 09:10 -0600, Andy Colson wrote:
> I know its been discussed before, and one big problem is license and
> patent problems.
Would like to see a design for that. There's a few different ways we
might want to do that, and I'm interested to see if its possible to get
compressed
On Dec 28, 2010, at 10:33 AM, Joachim Wieland wrote:
> On Tue, Dec 28, 2010 at 10:10 AM, Andy Colson wrote:
>> I know its been discussed before, and one big problem is license and patent
>> problems.
>>
>> Would this project be a problem:
>>
>> http://oldhome.schmorp.de/marc/liblzf.html
>
> It
On Tue, Dec 28, 2010 at 10:10 AM, Andy Colson wrote:
> I know its been discussed before, and one big problem is license and patent
> problems.
>
> Would this project be a problem:
>
> http://oldhome.schmorp.de/marc/liblzf.html
It looks like even liblzf is not going to be accepted. I have proposed
I know its been discussed before, and one big problem is license and
patent problems.
Would this project be a problem:
http://oldhome.schmorp.de/marc/liblzf.html
-Andy
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postg
