Date: Sun, 20 Mar 2005 00:52:45 +0100
To: "Josh Berkus" <josh@agliodbs.com>,
	pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning? 
References: <200503191202.38089.josh@agliodbs.com>
	<2092.1111273359@sss.pgh.pa.us> <op.snwojdwith1vuj@localhost>
From: PFC <lists@boutiquenumerique.com>
Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?=
Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <op.snwsl7v7th1vuj@localhost>
In-Reply-To: <2092.1111273359@sss.pgh.pa.us>
User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987)


> tableoid would accomplish that already, assuming that the "partitioned
> table" is effectively a view on separate physical tables.
>
> 			regards, tom lane

	Very good.

	Also note the possibility to mark a partition READ ONLY. Or even a table.
	It does not seem very useful but just think that for instance the "1999",  
"2000" ... "2004" partitions of a big archive probably never change.  
READLONY means we're sure they never change, thus no need to backup them  
every time. Keeping the example of some DB arranged by years / current  
year / current month, Just backup the "current month" part every day and  
the "current year" every month when you switch partitions.
	This could be achieved also by storing the time of last modification of a  
table somewhere.