Stephen Frost <sfr...@snowman.net> writes: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> (I'm a little more concerned by Alvaro's apparent position that WARM >> is a done deal; I didn't think so. This particular change seems like >> good cleanup anyhow, however.)
> Agreed. BTW, the reason I think it's good cleanup is that it's something that my colleagues at Salesforce also had to do as part of putting PG on top of a different storage engine that had different ideas about index handling. Essentially it's providing a bit of abstraction as to whether catalog storage is exactly heaps or not (a topic I've noticed Robert is starting to take some interest in, as well). However, the patch misses an important part of such an abstraction layer by not also converting catalog-related simple_heap_delete() calls into some sort of CatalogTupleDelete() operation. It is certainly a peculiarity of PG heaps that deletions don't require any immediate index work --- most other storage engines would need that. I propose that we should finish the job by inventing CatalogTupleDelete(), which for the moment would be a trivial wrapper around simple_heap_delete(), maybe just a macro for it. If there's no objections I'll go make that happen in a day or two. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers