Alter statement_timeout on existing pool. #2016

Activity

1. sehrope commented on Nov 29, 2019

   

   sehrope

   on Nov 29, 2019

   Contributor

   More actions

   There's nothing built-in to support this but you can do it with a custom wrapper:

   const DEFAULT_STATEMENT_TIMEOUT_MILLIS = 10 * 1000;
   
   const pool = new pg.Pool({ 
       statement_timeout: DEFAULT_STATEMENT_TIMEOUT_MILLIS,
    });
   
   const customQuery = async (query, params) => {
       const client = await pool.connect();
       try {
           // Set our custom timeout:
           await client.query('SET statement_timeout = 0');
           
           // Run the query
           const result = await client.query(query, params);
   
           // Revert the timeout
           await client.query(`SET statement_timeout = ${DEFAULT_STATEMENT_TIMEOUT_MILLIS}`);
   
           // All successful so release the connection:
           await client.release();
   
           // Return back the actual result from the executed command
           return result;
       } catch (err) {
           // Some error so discard the connection
           await client.release(err);
   
           // Bubble up the error
           throw err;
       }
   }

   ❤️React with ❤️1Reacted by Juan Hoyos
2. charmander commented on Nov 30, 2019

   

   charmander

   on Nov 30, 2019

   Collaborator

   More actions

   You could also have a separate pool for long queries. Its use of resources isn’t as nice, but it is simple.
3. dbauszus-glx commented on Dec 1, 2019

   

   dbauszus-glx

   on Dec 1, 2019

   Author

   More actions

   That works great. I already had my query in an async function anyways. Thanks for your help.
4. dbauszus-glx

   closed this as completedon Dec 1, 2019