[HACKERS] ARCHIVE TABLES (was: possible TODO: read-only tables, select from indexes only.)

2005-05-02 Thread Hannu Krosing
Third repeat post. Sorry if previous ones suddenly pop up too. ARCHIVE TABLES this is a further development ofthe read-only tables proposal, WHich answers Tom's question - 'how such a tables comes to exists' and inspired by someones (can't find the mail, sorry) suggestion to think of them as

Re: [HACKERS] ARCHIVE TABLES (was: possible TODO: read-only tables, select from indexes only.)

2005-05-02 Thread Jim C. Nasby
Out of curiosity, what would be required to allow deletes (but not updates)? My thinking is that you'd want *some* way to be able to prune data. Since you won't want to store an entire XID/CID for the delete, I think it would be acceptable to keep a table of XID/CID values for deletes and just

Re: [HACKERS] ARCHIVE TABLES (was: possible TODO: read-only tables, select from indexes only.)

2005-05-02 Thread Jochem van Dieten
On 5/2/05, Jim C. Nasby wrote: Out of curiosity, what would be required to allow deletes (but not updates)? The same as updates (because updates are essentially a delete + insert). My thinking is that you'd want *some* way to be able to prune data. Since you won't want to store an entire