From: PFC <lists@boutiquenumerique.com>
To: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Sun, 20 Mar 2005 00:52:45 +0100
Message-ID: <op.snwsl7v7th1vuj@localhost> (raw)
In-Reply-To: <2092.1111273359@sss.pgh.pa.us>
References: <200503191202.38089.josh@agliodbs.com>
<2092.1111273359@sss.pgh.pa.us>
<op.snwojdwith1vuj@localhost>
> 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.
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: lists@boutiquenumerique.com, josh@agliodbs.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <op.snwsl7v7th1vuj@localhost>
* 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