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 <[EMAIL PROTECTED]>
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
