Gregory Stark wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text fields.
Tree structures like file paths in particular.
You kind of want to do avoid both
Heikki Linnakangas [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text fields.
Tree structures like file paths in
[EMAIL PROTECTED] (Gregory Stark) writes:
Heikki Linnakangas [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text
On Wed, 2007-08-15 at 06:51 +0100, Heikki Linnakangas wrote:
Jeff Davis wrote:
On Tue, 2007-08-14 at 16:27 -0500, Decibel! wrote:
Isn't this what Grouped Index Tuples is?
http://community.enterprisedb.com/git/git-readme.txt
It looks like GIT is a little different.
GIT actually
On 8/14/07, Chris Browne [EMAIL PROTECTED] wrote:
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective implementations,
seeing some similarities and
On Wed, 2007-08-15 at 06:51 +0100, Heikki Linnakangas wrote:
What Chris is suggesting is basically a special case of GIT, where all
the heap tuples represented by an index tuple have the same key. I was
actually thinking of adding a flag to index tuples to indicate that
special case in GIT. We
Dawid Kuroczko wrote:
Some time ago I've had an idea that it might be possible to compress
th index size, even if it is a unique index. Take the path example.
My idea would be to to split indexed value to 8-byte chunks.
For example: /var/lib/postgresql/8.2/main would be split into:
[EMAIL PROTECTED] (Dawid Kuroczko) writes:
On 8/14/07, Chris Browne [EMAIL PROTECTED] wrote:
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective
Heikki Linnakangas [EMAIL PROTECTED] writes:
That general approach of storing a common part leading part just once is
called prefix compression. Yeah, it helps a lot on long text fields.
Tree structures like file paths in particular.
You kind of want to do avoid both the prefix and the
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective implementations,
seeing some similarities and differences. He pointed out one aspect
of index handling
Isn't this what Grouped Index Tuples is?
On Tue, Aug 14, 2007 at 05:21:16PM -0400, Chris Browne wrote:
I recently had a chat with someone who was pretty intimate with Adabas
for a number of years who's in the process of figuring things out
about PostgreSQL. We poked at bits of the respective
On Tue, 2007-08-14 at 16:27 -0500, Decibel! wrote:
Isn't this what Grouped Index Tuples is?
http://community.enterprisedb.com/git/git-readme.txt
It looks like GIT is a little different.
GIT actually stores a lower-bound key of a contiguous* range of keys
that all point to the same page, and
Jeff Davis wrote:
On Tue, 2007-08-14 at 16:27 -0500, Decibel! wrote:
Isn't this what Grouped Index Tuples is?
http://community.enterprisedb.com/git/git-readme.txt
It looks like GIT is a little different.
GIT actually stores a lower-bound key of a contiguous* range of keys
that all
13 matches
Mail list logo
