Re: Declarative partitioning grammar
Markus Wanner <markus@bluegap.ch>
From: Markus Schiltknecht <markus@bluegap.ch>
To: Zeugswetter Andreas ADI SD <Andreas.Zeugswetter@s-itsolutions.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Jeff Cohen <jcohen@greenplum.com>, Warren Turkal <turkal@google.com>, Ron Mayer <rm_pg@cheapcomplexdevices.com>, Gavin Sherry <swm@alcove.com.au>, pgsql-hackers@postgresql.org
Date: 2008-01-15T16:59:37Z
Lists: pgsql-hackers
Hi, (sorry for the previous one, if delivered, that went of too early...) Zeugswetter Andreas ADI SD wrote: > Yes, but the problem with the timestamp partitioned tables is, that the > window is sliding. Thus you would need two alter tables for each new > period. One that changes the constraint + one that creates the new > partition. So it seems natural to join the two concepts for such a > partitioning syntax. If you think in terms of split points, having to alter two partitions isn't true, you just add a split point. Of course, that also alters the "constraints" of the partitions, but I think we all agree that the system should maintain those constraints automatically, anyway. As such, they don't even have to be visible to the DBA. > Personally I find the automatic partition idea intriguing, where you > only have to choose an expression that equates to one value (value > group) per partition (and possibly a way to derive a partition name). IMO, better go right to a fully automated approach. Or why would you need partition names in such a case? Regards Markus