Re: A more general approach (Re: [HACKERS] Data archiving/warehousing idea)

2007-02-02 Thread Hannu Krosing
Ühel kenal päeval, N, 2007-02-01 kell 12:31, kirjutas Tom Lane: Hannu Krosing [EMAIL PROTECTED] writes: A more radical variation of the restricted-use archive table approach is storing all tuple visibility info in a separate file. At first it seems to just add overhead, but for lots (most ?

A more general approach (Re: [HACKERS] Data archiving/warehousing idea)

2007-02-01 Thread Hannu Krosing
Ühel kenal päeval, N, 2007-02-01 kell 13:24, kirjutas Gavin Sherry: A different approach discussed earlier involves greatly restricting the way in which the table is used. This table could only be written to if an exclusive lock is held; on error or ABORT, the table is truncated. The

Re: A more general approach (Re: [HACKERS] Data archiving/warehousing idea)

2007-02-01 Thread Hannu Krosing
Ühel kenal päeval, N, 2007-02-01 kell 14:38, kirjutas Hannu Krosing: Ühel kenal päeval, N, 2007-02-01 kell 13:24, kirjutas Gavin Sherry: A different approach discussed earlier involves greatly restricting the way in which the table is used. This table could only be written to if an

Re: A more general approach (Re: [HACKERS] Data archiving/warehousing idea)

2007-02-01 Thread Tom Lane
Hannu Krosing [EMAIL PROTECTED] writes: A more radical variation of the restricted-use archive table approach is storing all tuple visibility info in a separate file. At first it seems to just add overhead, but for lots (most ? ) usecases the separately stored visibility should be highly