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 0D7E4569B5 for ; Tue, 22 Mar 2005 15:59:25 +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 77103-08 for ; Tue, 22 Mar 2005 15:59:22 +0000 (GMT) Received: from fuji.krosing.net (joltid-gw.joltid.org [195.50.194.24]) by svr1.postgresql.org (Postfix) with ESMTP id F112F569B2 for ; Tue, 22 Mar 2005 15:59:20 +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 j2MFxHqK006020; Tue, 22 Mar 2005 17:59:17 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.13.1/8.13.1/Submit) id j2MFxG0K006019; Tue, 22 Mar 2005 17:59:16 +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: Alvaro Herrera Cc: PFC , Josh Berkus , pgsql-performance@postgresql.org In-Reply-To: <20050322131000.GA15881@dcc.uchile.cl> References: <200503191202.38089.josh@agliodbs.com> <2092.1111273359@sss.pgh.pa.us> <1111429584.4675.40.camel@fuji.krosing.net> <20050322131000.GA15881@dcc.uchile.cl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 22 Mar 2005 17:59:16 +0200 Message-Id: <1111507156.5724.1.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=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/450 X-Sequence-Number: 11155 On T, 2005-03-22 at 09:10 -0400, Alvaro Herrera wrote: > On Mon, Mar 21, 2005 at 08:26:24PM +0200, Hannu Krosing wrote: > > On P, 2005-03-20 at 00:52 +0100, PFC wrote: > > > > Also note the possibility to mark a partition READ ONLY. Or even a table. > > > Would we still need regular VACUUMing of read-only table to avoid > > OID-wraparound ? > > You could VACUUM FREEZE the table or partition, so you wouldn't need to > vacuum it again. But when I do just VACUUM; will this know to avoid vacuuming VACUUM FREEZE'd partitions ? Or could this be somehow liked to READ ONLY + VACUUM FREEZE state ? -- Hannu Krosing