pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jaime Casanova <systemguards@gmail.com>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: Maintaining cluster order on insert
Date: Tue, 10 Jul 2007 12:43:06 +0100
Message-ID: <469370CA.1060608@enterprisedb.com> (raw)
In-Reply-To: <87odikzems.fsf@oxford.xeocode.com>
References: <200705152223.l4FMNJa17969@momjian.us>
<464A33AB.1050401@enterprisedb.com>
<20070516003810.GI20707@nasby.net>
<464B15EF.4000808@enterprisedb.com>
<c2d9e70e0705172153g3207adb6kd4abdfdf3a9215ff@mail.gmail.com>
<464D96D6.1030608@enterprisedb.com>
<457.1184023772@sss.pgh.pa.us>
<87odikzems.fsf@oxford.xeocode.com>
Gregory Stark wrote:
> It's pretty serious what you're suggesting since it means that we'll basically
> never have a real cluster feature. I would sure hope we're missing something
> and there's a way to make this work usefully.
Another approach would be an online CLUSTER command. That means there'll
be a lot of churn when tuples need to be moved back and forth, along
with updating indexes, but it'd take the overhead out of the critical path.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
view thread (46+ messages) latest in thread
Message-ID: <469370CA.1060608@enterprisedb.com> Permalink: ../469370CA.1060608@enterprisedb.com/ Also on: postgresql.org/message-id/469370CA.1060608@enterprisedb.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-hackers@postgresql.org Cc: heikki@enterprisedb.com, stark@enterprisedb.com, tgl@sss.pgh.pa.us, systemguards@gmail.com, decibel@decibel.org, bruce@momjian.us, pgsql-patches@postgresql.org Subject: Re: Maintaining cluster order on insert In-Reply-To: <469370CA.1060608@enterprisedb.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
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