On Fri, Feb 17, 2012 at 10:19 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> What if you did this ONCE and wrote the results to a file someplace? > > That's still a cache, you've just defaulted on your obligation to think > about what conditions require the cache to be flushed.
Yep. Unfortunately, I don't have a good idea how to handle that; I was hoping someone else did. > Before going much further with this, we should probably do some timings > of 64K calls of iswupper and friends, just to see how bad a dumb > implementation will be. Can't hurt. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
