I am working on a research project that looks at an entire database access layer written against a normalized database and suggests de-normalizations to be done to the database structure. In effect looking at de-normalizations as a kind of cache. I am looking for any code I can leverage to do this work.
As documentation for the plan optimizer I found the document below. Is this still relatively accurate? http://www.postgresql.org/files/developer/optimizer.pdf I have looked at the postgresql optimizer code years ago. And it was not too hard to follow. I wonder if it is fairly independent from the rest of the system. Or if anyone has suggestions of using a different optimizer codebase. Here is a discussion I found here from years ago. http://postgresql.1045698.n5.nabble.com/About-method-of-PostgreSQL-s-Optimizer-td1933859.html -- View this message in context: http://postgresql.1045698.n5.nabble.com/De-normalization-optimizer-research-project-tp5769655.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
