What would happen if I run two SQL commands using the same DB connection?












1















I'm writing a program to run mass calculation and output results into PostgreSQL.



My platform is Windows Sever 2008, PostgreSQL 10. My program is written in C.



The results would be produced group by group, finishing of each group will create an extra thread to write the output.



Now since the output threads are created one by one, it is possible that two or more SQL input commands will be created simultaneously, or the previous one is under process when new ones call the function.



So my questions are:



(1) What would happen if one thread is in SQL processing and another thread called PQexec(PGconn *conn, const char *query), would they effect each other?



(2) What if I apply different PGconn? Would it speed up?










share|improve this question





























    1















    I'm writing a program to run mass calculation and output results into PostgreSQL.



    My platform is Windows Sever 2008, PostgreSQL 10. My program is written in C.



    The results would be produced group by group, finishing of each group will create an extra thread to write the output.



    Now since the output threads are created one by one, it is possible that two or more SQL input commands will be created simultaneously, or the previous one is under process when new ones call the function.



    So my questions are:



    (1) What would happen if one thread is in SQL processing and another thread called PQexec(PGconn *conn, const char *query), would they effect each other?



    (2) What if I apply different PGconn? Would it speed up?










    share|improve this question



























      1












      1








      1








      I'm writing a program to run mass calculation and output results into PostgreSQL.



      My platform is Windows Sever 2008, PostgreSQL 10. My program is written in C.



      The results would be produced group by group, finishing of each group will create an extra thread to write the output.



      Now since the output threads are created one by one, it is possible that two or more SQL input commands will be created simultaneously, or the previous one is under process when new ones call the function.



      So my questions are:



      (1) What would happen if one thread is in SQL processing and another thread called PQexec(PGconn *conn, const char *query), would they effect each other?



      (2) What if I apply different PGconn? Would it speed up?










      share|improve this question
















      I'm writing a program to run mass calculation and output results into PostgreSQL.



      My platform is Windows Sever 2008, PostgreSQL 10. My program is written in C.



      The results would be produced group by group, finishing of each group will create an extra thread to write the output.



      Now since the output threads are created one by one, it is possible that two or more SQL input commands will be created simultaneously, or the previous one is under process when new ones call the function.



      So my questions are:



      (1) What would happen if one thread is in SQL processing and another thread called PQexec(PGconn *conn, const char *query), would they effect each other?



      (2) What if I apply different PGconn? Would it speed up?







      postgresql






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 15 '18 at 6:06









      Laurenz Albe

      49k102848




      49k102848










      asked Nov 15 '18 at 5:50









      ShoreShore

      748




      748
























          1 Answer
          1






          active

          oldest

          votes


















          2














          If you try to call PQexec on a connection that is in the process of executing an SQL statement, you would cause a protocol violation. That just doesn't work.



          Processing could certainly be made faster if you use several database connections in parallel — concurrent transactions is something that PostgreSQL is designed for.






          share|improve this answer
























          • Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

            – Shore
            Nov 15 '18 at 6:11













          • Yes, absolutely.

            – Laurenz Albe
            Nov 15 '18 at 6:12











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f53313202%2fwhat-would-happen-if-i-run-two-sql-commands-using-the-same-db-connection%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









          2














          If you try to call PQexec on a connection that is in the process of executing an SQL statement, you would cause a protocol violation. That just doesn't work.



          Processing could certainly be made faster if you use several database connections in parallel — concurrent transactions is something that PostgreSQL is designed for.






          share|improve this answer
























          • Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

            – Shore
            Nov 15 '18 at 6:11













          • Yes, absolutely.

            – Laurenz Albe
            Nov 15 '18 at 6:12
















          2














          If you try to call PQexec on a connection that is in the process of executing an SQL statement, you would cause a protocol violation. That just doesn't work.



          Processing could certainly be made faster if you use several database connections in parallel — concurrent transactions is something that PostgreSQL is designed for.






          share|improve this answer
























          • Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

            – Shore
            Nov 15 '18 at 6:11













          • Yes, absolutely.

            – Laurenz Albe
            Nov 15 '18 at 6:12














          2












          2








          2







          If you try to call PQexec on a connection that is in the process of executing an SQL statement, you would cause a protocol violation. That just doesn't work.



          Processing could certainly be made faster if you use several database connections in parallel — concurrent transactions is something that PostgreSQL is designed for.






          share|improve this answer













          If you try to call PQexec on a connection that is in the process of executing an SQL statement, you would cause a protocol violation. That just doesn't work.



          Processing could certainly be made faster if you use several database connections in parallel — concurrent transactions is something that PostgreSQL is designed for.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 6:04









          Laurenz AlbeLaurenz Albe

          49k102848




          49k102848













          • Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

            – Shore
            Nov 15 '18 at 6:11













          • Yes, absolutely.

            – Laurenz Albe
            Nov 15 '18 at 6:12



















          • Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

            – Shore
            Nov 15 '18 at 6:11













          • Yes, absolutely.

            – Laurenz Albe
            Nov 15 '18 at 6:12

















          Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

          – Shore
          Nov 15 '18 at 6:11







          Which means that if I give each thread 1 dbconnection, it should be fine for simultaneously insertion of results??

          – Shore
          Nov 15 '18 at 6:11















          Yes, absolutely.

          – Laurenz Albe
          Nov 15 '18 at 6:12





          Yes, absolutely.

          – Laurenz Albe
          Nov 15 '18 at 6:12




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f53313202%2fwhat-would-happen-if-i-run-two-sql-commands-using-the-same-db-connection%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

          Florida Star v. B. J. F.

          Error while running script in elastic search , gateway timeout

          Adding quotations to stringified JSON object values