Re: [PATCHES] CREATE TABLE LIKE INCLUDING INDEXES support

[Gregory Stark]

Jim C. Nasby [EMAIL PROTECTED] writes:

 On Fri, Jul 20, 2007 at 12:40:46PM +0100, Gregory Stark wrote:

 One of the main use cases I envision is wanting to create new partitions
 suitable for being added to a partitioned table.

 Except that's normally done with CREATE TABLE INHERITS, which seems
 cleaner to me. I think the patch would be more useful if it added
 support for INHERITS, but I don't object to it as-is.

Well there are two different approaches to creating a new partition. For some
use cases you want to create a new empty partition directly in the table and
start using it right away. For other use cases you want to create a table into
which you need to load data, possibly even massage the data with updates and
deletes or additional inserts, then add the partition with the data all ready
directly into the master table.

-- 
  Gregory Stark
  EnterpriseDB  http://www.enterprisedb.com


---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Re: [PATCHES] Updated bitmap index patch

[Simon Riggs]

On Thu, 2007-05-17 at 18:20 -0400, Alvaro Herrera wrote:
 Bruce Momjian wrote:
  
  Due to unfinished VACUUM:
  
  This has been saved for the 8.4 release:
  
  http://momjian.postgresql.org/cgi-bin/pgpatches_hold
 
 While we're at this, let's consider Heikki's patch for the streaming
 indexscan API stuff.  That patch was supposed to come from the bitmap
 index patch, but it was also supposed to help the Grouped Index Tuples
 (GIT) patch.
 
 In fact, as far as I understood the discussion, GIT would be helped by
 the streaming indexscan API patch, because it would help de-uglify
 certain parts of that patch.  It is my impression that we would not want
 to commit the ugly GIT patch; so it would mean that either we commit the
 streaming indexscan patch first, and a beautiful GIT patch shortly later,
 or we don't commit any of them.
 
 So, the question is: do we want the GIT patch in 8.3?  If we do, then we
 need the streaming indexscan API patch.  And thus we would need an
 updated (beautiful) GIT patch.
 
 Is there a resolution on this?  Alexey Kluykin and I would be interested
 in helping review this set of patches, if it is decided that they are
 wanted for 8.3.
 
 I want to point out that the GIT patch is one of the things sitting in
 the reviewing queue from very early.

Alvaro,

As you note above there is some linkage between bit map indexes and
clustered indexes, so it seems like we'll either get both or neither.

I notice the GIT patch is being listed as under review by Alexey and
yourself. Are you actively working on this, or is anyone else planning
on working on this review? 

I'd like to help where I can if nobody else is currently doing this. I
would focus initially on some analysis of the various use cases to give
a better view on what we would need B-tree, clustered indexes and bitmap
indexes to do for us.

-- 
  Simon Riggs
  EnterpriseDB  http://www.enterprisedb.com


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster