2010/6/24 Josh Berkus <josh@xxxxxxxxxxxx>: > >> And I'm also planning to implement unlogged tables, which have the >> same contents for all sessions but are not WAL-logged (and are >> truncated on startup). this is similar MySQL's memory tables. Personally, I don't see any practical sense do same work on PostgreSQL now, when memcached exists. Much more important is smarter cache controlling then we have now - maybe with priorities for some tables and some operations (applications) - sometimes we don't need use cache for extra large scans. Regards Pavel Stehule > > Yep. And it's quite possible that this will be adequate for most users. > > And it's also possible that the extra CPU which Robert isn't getting rid > of (bgwriter, checkpointing, etc.) does not have a measurable impact on > performance. At this point, my idea (which I call > "RunningWithScissorsDB") is only an idea for experimentation and > performance testing. It's pretty far off from being a TODO. > > -- > -- Josh Berkus > PostgreSQL Experts Inc. > http://www.pgexperts.com > > -- > Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
