X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 11FB3569C2 for ; Tue, 22 Mar 2005 11:29:44 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88112-02 for ; Tue, 22 Mar 2005 11:29:34 +0000 (GMT) Received: from fuji.krosing.net (joltid-gw.joltid.org [195.50.194.24]) by svr1.postgresql.org (Postfix) with ESMTP id DF38D563E9 for ; Tue, 22 Mar 2005 11:29:33 +0000 (GMT) Received: from fuji.krosing.net (localhost [127.0.0.1]) by fuji.krosing.net (8.13.1/8.13.1) with ESMTP id j2LIQPC6005831; Mon, 21 Mar 2005 20:26:26 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.13.1/8.13.1/Submit) id j2LIQPT8005830; Mon, 21 Mar 2005 20:26:25 +0200 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: What needs to be done for real Partitioning? From: Hannu Krosing To: PFC Cc: Josh Berkus , pgsql-performance@postgresql.org In-Reply-To: References: <200503191202.38089.josh@agliodbs.com> <2092.1111273359@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 21 Mar 2005 20:26:24 +0200 Message-Id: <1111429584.4675.40.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-1) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/435 X-Sequence-Number: 11140 On P, 2005-03-20 at 00:52 +0100, PFC wrote: > > 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. Would we still need regular VACUUMing of read-only table to avoid OID-wraparound ? -- Hannu Krosing