pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedBlock B-tree etc. (was Re: Introducing an advanced Frequent Update)
3+ messages / 3 participants
[nested] [flat]
* Block B-tree etc. (was Re: Introducing an advanced Frequent Update)
@ 2006-11-07 09:51 Heikki Linnakangas <heikki@enterprisedb.com>
2006-11-07 17:24 ` Re: Block B-tree etc. (was Re: Introducing an advanced Frequent Update) Josh Berkus <josh@agliodbs.com>
2006-11-08 05:00 ` Re: Block B-tree etc. (was Re: Introducing an advanced Frequent Luke Lonergan <llonergan@greenplum.com>
0 siblings, 2 replies; 3+ messages in thread
From: Heikki Linnakangas @ 2006-11-07 09:51 UTC (permalink / raw)
To: Luke Lonergan <LLonergan@greenplum.com>; +Cc: Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers
Luke Lonergan wrote:
> Simon,
>
> Bring it on! We at GP have been evaluating various approaches to index
> organized tables which unify index with heap storage to solve some of
> the problems you mention. Split index and heap is a big issue in
> Postgres and we'd all welcome a good solution to it, even for limited
> circumstances like single index organization or the like.
I don't think Simon's proposal is meant to address that issue, but did
you follow the thread I started in September about Block B-Tree index:
http://archives.postgresql.org/pgsql-hackers/2006-09/msg02041.php
That's our plan to achieve speedups that other DBMS's have achieved with
Index-Organized-Tables or Clustered Indexes. We're running initial
performance tests of it as we speak, and if all goes well we're hoping
to get that into PostgreSQL 8.3.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Block B-tree etc. (was Re: Introducing an advanced Frequent Update)
2006-11-07 09:51 Block B-tree etc. (was Re: Introducing an advanced Frequent Update) Heikki Linnakangas <heikki@enterprisedb.com>
@ 2006-11-07 17:24 ` Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 3+ messages in thread
From: Josh Berkus @ 2006-11-07 17:24 UTC (permalink / raw)
To: pgsql-hackers; +Cc: Heikki Linnakangas <heikki@enterprisedb.com>; Luke Lonergan <LLonergan@greenplum.com>; Simon Riggs <simon@2ndquadrant.com>
Luke,
> That's our plan to achieve speedups that other DBMS's have achieved with
> Index-Organized-Tables or Clustered Indexes. We're running initial
> performance tests of it as we speak, and if all goes well we're hoping
> to get that into PostgreSQL 8.3.
Also, if the EDB folks weren't clear, the two proposals are meant to
compliment each other.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Block B-tree etc. (was Re: Introducing an advanced Frequent
2006-11-07 09:51 Block B-tree etc. (was Re: Introducing an advanced Frequent Update) Heikki Linnakangas <heikki@enterprisedb.com>
@ 2006-11-08 05:00 ` Luke Lonergan <llonergan@greenplum.com>
1 sibling, 0 replies; 3+ messages in thread
From: Luke Lonergan @ 2006-11-08 05:00 UTC (permalink / raw)
To: Heikki Linnakangas <heikki@enterprisedb.com>; +Cc: Simon Riggs <simon@2ndquadrant.com>; pgsql-hackers
Heikki,
On 11/7/06 1:51 AM, "Heikki Linnakangas" <heikki@enterprisedb.com> wrote:
> I don't think Simon's proposal is meant to address that issue, but did
> you follow the thread I started in September about Block B-Tree index:
> http://archives.postgresql.org/pgsql-hackers/2006-09/msg02041.php
Aha - mystery solved - thanks for the clarification.
Block Btree ~= Lossy Btree
- Luke
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-11-08 05:00 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-11-07 09:51 Block B-tree etc. (was Re: Introducing an advanced Frequent Update) Heikki Linnakangas <heikki@enterprisedb.com>
2006-11-07 17:24 ` Josh Berkus <josh@agliodbs.com>
2006-11-08 05:00 ` Re: Block B-tree etc. (was Re: Introducing an advanced Frequent Luke Lonergan <llonergan@greenplum.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox