postgres - c = not working for postgres 11 in docker The Next CEO of Stack OverflowDegrading...

Is there a difference between "Fahrstuhl" and "Aufzug"

What connection does MS Office have to Netscape Navigator?

Rotate a column

Why don't programming languages automatically manage the synchronous/asynchronous problem?

Is it possible to search for a directory/file combination?

Received an invoice from my ex-employer billing me for training; how to handle?

If Nick Fury and Coulson already knew about aliens (Kree and Skrull) why did they wait until Thor's appearance to start making weapons?

Is "for causing autism in X" grammatical?

Help understanding this unsettling image of Titan, Epimetheus, and Saturn's rings?

What happened in Rome, when the western empire "fell"?

Interfacing a button to MCU (and PC) with 50m long cable

Inappropriate reference requests from Journal reviewers

Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?

I believe this to be a fraud - hired, then asked to cash check and send cash as Bitcoin

Limits on contract work without pre-agreed price/contract (UK)

Would a galaxy be visible from outside, but nearby?

Novel about a guy who is possessed by the divine essence and the world ends?

How fast would a person need to move to trick the eye?

What benefits would be gained by using human laborers instead of drones in deep sea mining?

How do I make a variable always equal to the result of some calculations?

Is there a way to save my career from absolute disaster?

Are there any unintended negative consequences to allowing PCs to gain multiple levels at once in a short milestone-XP game?

How to avoid supervisors with prejudiced views?

How powerful is the invisibility granted by the Gloom Stalker ranger's Umbral Sight feature?



postgres - c = not working for postgres 11 in docker



The Next CEO of Stack OverflowDegrading PostgreSQL 8.4 write performanceOptimizing ORDER BY in a full text search queryFinding the current prices for n Fuelstations at a certain point in timeSampling and matching samples with spatial conditionsPostgreSQL pg_upgrade --link mode performance issue after upgradepostgresql + pgbouncer, idle server and high cl_waitingRunning psql/postgres client in an ephemeral mode in a containerHow to relax file permissions conditions on postgres database folder?SMO, SSMS are slow for management of SQL Server in Docker when connecting to localhostExcessive Postgres Docker CPU Consumption












0















I'm running a Postgres inside a docker. I want to change the default config of Postgres so I'm running :



docker container run -d postgres -c max_connections=200 -c shared_buffers = 1GB -c effective_cache_size=3GB -c maintenance_work_mem=256MB -c checkpoint_completion_target=0.7 -c wal_buffers=16MB 


But when I'm connecting to Postgres running:



 docker exec -it container_name psql


And then the result of :



SHOW max_connections;


is



 max_connections
-----------------
100
(1 row)


And it's not just max_connections. None of the parameters are changed. And I don't know what is the problem with what I'm doing?



Update: I already have a running docker container and I want it to apply these parameters to it without needing to restart it.










share|improve this question
















bumped to the homepage by Community 38 secs ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I'm running a Postgres inside a docker. I want to change the default config of Postgres so I'm running :



    docker container run -d postgres -c max_connections=200 -c shared_buffers = 1GB -c effective_cache_size=3GB -c maintenance_work_mem=256MB -c checkpoint_completion_target=0.7 -c wal_buffers=16MB 


    But when I'm connecting to Postgres running:



     docker exec -it container_name psql


    And then the result of :



    SHOW max_connections;


    is



     max_connections
    -----------------
    100
    (1 row)


    And it's not just max_connections. None of the parameters are changed. And I don't know what is the problem with what I'm doing?



    Update: I already have a running docker container and I want it to apply these parameters to it without needing to restart it.










    share|improve this question
















    bumped to the homepage by Community 38 secs ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I'm running a Postgres inside a docker. I want to change the default config of Postgres so I'm running :



      docker container run -d postgres -c max_connections=200 -c shared_buffers = 1GB -c effective_cache_size=3GB -c maintenance_work_mem=256MB -c checkpoint_completion_target=0.7 -c wal_buffers=16MB 


      But when I'm connecting to Postgres running:



       docker exec -it container_name psql


      And then the result of :



      SHOW max_connections;


      is



       max_connections
      -----------------
      100
      (1 row)


      And it's not just max_connections. None of the parameters are changed. And I don't know what is the problem with what I'm doing?



      Update: I already have a running docker container and I want it to apply these parameters to it without needing to restart it.










      share|improve this question
















      I'm running a Postgres inside a docker. I want to change the default config of Postgres so I'm running :



      docker container run -d postgres -c max_connections=200 -c shared_buffers = 1GB -c effective_cache_size=3GB -c maintenance_work_mem=256MB -c checkpoint_completion_target=0.7 -c wal_buffers=16MB 


      But when I'm connecting to Postgres running:



       docker exec -it container_name psql


      And then the result of :



      SHOW max_connections;


      is



       max_connections
      -----------------
      100
      (1 row)


      And it's not just max_connections. None of the parameters are changed. And I don't know what is the problem with what I'm doing?



      Update: I already have a running docker container and I want it to apply these parameters to it without needing to restart it.







      postgresql docker






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 2 '18 at 16:27







      Marzieh Heidari

















      asked Nov 30 '18 at 18:32









      Marzieh HeidariMarzieh Heidari

      1014




      1014





      bumped to the homepage by Community 38 secs ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 38 secs ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You cannot put spaces around the equals sign when using the "-c" option. So you need something like postgres -c max_connections=200



          When I try it with the spaces, it refused to start at all. So I don't know what you are connecting to in order to SHOW max_connections;. Maybe you already had a server running before you tried to start with the invalid syntax?






          share|improve this answer
























          • You are right. I already have a running server. But using the command without space did not work.

            – Marzieh Heidari
            Nov 30 '18 at 19:27











          • And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

            – Marzieh Heidari
            Nov 30 '18 at 19:31













          • I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

            – jjanes
            Nov 30 '18 at 20:02











          • You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

            – Marzieh Heidari
            Nov 30 '18 at 20:11














          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f223866%2fpostgres-c-parameter-value-not-working-for-postgres-11-in-docker%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          You cannot put spaces around the equals sign when using the "-c" option. So you need something like postgres -c max_connections=200



          When I try it with the spaces, it refused to start at all. So I don't know what you are connecting to in order to SHOW max_connections;. Maybe you already had a server running before you tried to start with the invalid syntax?






          share|improve this answer
























          • You are right. I already have a running server. But using the command without space did not work.

            – Marzieh Heidari
            Nov 30 '18 at 19:27











          • And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

            – Marzieh Heidari
            Nov 30 '18 at 19:31













          • I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

            – jjanes
            Nov 30 '18 at 20:02











          • You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

            – Marzieh Heidari
            Nov 30 '18 at 20:11


















          0














          You cannot put spaces around the equals sign when using the "-c" option. So you need something like postgres -c max_connections=200



          When I try it with the spaces, it refused to start at all. So I don't know what you are connecting to in order to SHOW max_connections;. Maybe you already had a server running before you tried to start with the invalid syntax?






          share|improve this answer
























          • You are right. I already have a running server. But using the command without space did not work.

            – Marzieh Heidari
            Nov 30 '18 at 19:27











          • And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

            – Marzieh Heidari
            Nov 30 '18 at 19:31













          • I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

            – jjanes
            Nov 30 '18 at 20:02











          • You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

            – Marzieh Heidari
            Nov 30 '18 at 20:11
















          0












          0








          0







          You cannot put spaces around the equals sign when using the "-c" option. So you need something like postgres -c max_connections=200



          When I try it with the spaces, it refused to start at all. So I don't know what you are connecting to in order to SHOW max_connections;. Maybe you already had a server running before you tried to start with the invalid syntax?






          share|improve this answer













          You cannot put spaces around the equals sign when using the "-c" option. So you need something like postgres -c max_connections=200



          When I try it with the spaces, it refused to start at all. So I don't know what you are connecting to in order to SHOW max_connections;. Maybe you already had a server running before you tried to start with the invalid syntax?







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 30 '18 at 19:21









          jjanesjjanes

          14.1k1017




          14.1k1017













          • You are right. I already have a running server. But using the command without space did not work.

            – Marzieh Heidari
            Nov 30 '18 at 19:27











          • And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

            – Marzieh Heidari
            Nov 30 '18 at 19:31













          • I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

            – jjanes
            Nov 30 '18 at 20:02











          • You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

            – Marzieh Heidari
            Nov 30 '18 at 20:11





















          • You are right. I already have a running server. But using the command without space did not work.

            – Marzieh Heidari
            Nov 30 '18 at 19:27











          • And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

            – Marzieh Heidari
            Nov 30 '18 at 19:31













          • I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

            – jjanes
            Nov 30 '18 at 20:02











          • You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

            – Marzieh Heidari
            Nov 30 '18 at 20:11



















          You are right. I already have a running server. But using the command without space did not work.

          – Marzieh Heidari
          Nov 30 '18 at 19:27





          You are right. I already have a running server. But using the command without space did not work.

          – Marzieh Heidari
          Nov 30 '18 at 19:27













          And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

          – Marzieh Heidari
          Nov 30 '18 at 19:31







          And with both spaced and not-spaced commands I get something like 35d1c90ef07bb73f4ad30951951498f574e125ba872404015d26006f3d013284 as result which I don't know what it means

          – Marzieh Heidari
          Nov 30 '18 at 19:31















          I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

          – jjanes
          Nov 30 '18 at 20:02





          I suspect that that hash value is being delivered by docker, not by postgres. You might need docker-specific help, rather than dba help, with that. If you already have a server running, you won't be able to start another one in the same container on the same port. What if you remove all the options and just try to start a default instance now?

          – jjanes
          Nov 30 '18 at 20:02













          You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

          – Marzieh Heidari
          Nov 30 '18 at 20:11







          You mean like docker-compose up -d? I get WARNING: Found orphan containers (mahan_postgres) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

          – Marzieh Heidari
          Nov 30 '18 at 20:11




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f223866%2fpostgres-c-parameter-value-not-working-for-postgres-11-in-docker%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...