On Mon, Oct 26, 2009 at 3:05 PM, Josh Berkus <j...@agliodbs.com> wrote: > I'm thinking an array, in case we want to make other tablespace cost > parameters in the future.* Or, better, whatever structure we're > currently using for ROLEs. > > (* for example, if someone does manage a filesystem with a separate > cache space per mount, then we'd want effective_cache_size to be > tablespace-based as well)
Still far from convinced on that one. But effective_io_concurrency should be included even in the first pass. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
