From: Hannu Krosing <hannu@tm.ee>
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: PFC <lists@boutiquenumerique.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Tue, 22 Mar 2005 17:59:16 +0200
Message-ID: <1111507156.5724.1.camel@fuji.krosing.net> (raw)
In-Reply-To: <20050322131000.GA15881@dcc.uchile.cl>
References: <200503191202.38089.josh@agliodbs.com>
<2092.1111273359@sss.pgh.pa.us>
<op.snwojdwith1vuj@localhost>
<op.snwsl7v7th1vuj@localhost>
<1111429584.4675.40.camel@fuji.krosing.net>
<20050322131000.GA15881@dcc.uchile.cl>
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 <hannu@tm.ee>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: hannu@tm.ee, alvherre@dcc.uchile.cl, lists@boutiquenumerique.com, josh@agliodbs.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <1111507156.5724.1.camel@fuji.krosing.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox