Adjust the effective_cache_size default for standalone backends
authorBruce Momjian <bruce@momjian.us>
Wed, 9 Oct 2013 03:53:39 +0000 (23:53 -0400)
committerBruce Momjian <bruce@momjian.us>
Wed, 9 Oct 2013 03:53:39 +0000 (23:53 -0400)
src/backend/postmaster/postmaster.c
src/backend/tcop/postgres.c

index e9bf121f542536ef058eac17303543d1ab4610c7..bd20e14ea57f15a922828b03a3e8ea27ece67467 100644 (file)
@@ -785,6 +785,8 @@ PostmasterMain(int argc, char *argv[])
    if (!SelectConfigFiles(userDoption, progname))
        ExitPostmaster(2);
 
+   set_default_effective_cache_size();
+
    if (output_config_variable != NULL)
    {
        /*
@@ -795,8 +797,6 @@ PostmasterMain(int argc, char *argv[])
        ExitPostmaster(0);
    }
 
-   set_default_effective_cache_size();
-
    /* Verify that DataDir looks reasonable */
    checkDataDir();
 
index 1eaf287eec9f4e08cdaca28142c5914ffbd718ff..4b2a7761af8dfa5e2072c34f78118a8a246fa1bb 100644 (file)
@@ -3592,6 +3592,8 @@ PostgresMain(int argc, char *argv[],
            proc_exit(1);
    }
 
+   set_default_effective_cache_size();
+       
    /*
     * You might expect to see a setsid() call here, but it's not needed,
     * because if we are under a postmaster then BackendInitialize() did it.