Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e5DP5-00075m-H1 for pgsql-performance@arkaria.postgresql.org; Thu, 19 Oct 2017 16:10:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e5DP4-00026s-Tz for pgsql-performance@arkaria.postgresql.org; Thu, 19 Oct 2017 16:10:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e5DP4-00026f-E5 for pgsql-performance@postgresql.org; Thu, 19 Oct 2017 16:10:38 +0000 Received: from mail-vk0-x235.google.com ([2607:f8b0:400c:c05::235]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e5DP1-0005B5-Tm for pgsql-performance@postgresql.org; Thu, 19 Oct 2017 16:10:37 +0000 Received: by mail-vk0-x235.google.com with SMTP id 137so5662180vkk.8 for ; Thu, 19 Oct 2017 09:10:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=POh6QjC3Tz7sbqw2+BJUX8TDO2cHDycuhha+lATbg3s=; b=LGnPRKM4WjyfE8Fu855PYfMPP3XV8yZvfrTZNUfYfT73qMt8E9DmT7jES9KsQ2ezUu g8pKLGAbimi60YPMzWgmFnNd6X3StDtC7XFFCyZ3p0XZ5z9JOjvsU8tnirncyHQPbjKI ftSkPfAtdU7x1RPyy1nDWt9KvOHUz/Se8/z2UifMaZWREE7zLJPxdlNF3+UdA+6onz1o FSC+OAYl79GuG2GKkAqA2VQVFZJWHSUr46RfKCSk/UMwXNQMhQhFJ3L9rOk8ZH3kSD42 l06FLvc5K80ej49O+ELV7orX7Csb5jMw4t4s8ZUWgzFZpJzaD6K+VEX1H2hch10w8fNW bJog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=POh6QjC3Tz7sbqw2+BJUX8TDO2cHDycuhha+lATbg3s=; b=MBjRo2HpHfy5K75V+WZC4MS5gosdzyOTbldKt4p5wTT50fEVODG7N9CjFWYDh4j+iM dMxAzcuYvu24shj8VRHldkjWnm2SxILtnJqfFj90dnyyeuGnlYO+JIhsjGIDF+tKvU7z 8FEoTOdgo2PS1Ap7dNlS4/VPTlQ2FwQs5PJO0osI0W3ySTjvs2WRRmMuhU31M07UG4YC Oj/fE82ox1PSJPwvUohCfQYja++rz8VStTLRvldNm4UahbN91y1VL60gtdNTyQHDoi1E Vq9Mvf/yKsqTEgUzPozfpPQVPKphjUH6eo+otPZXvVJ4/mJtNpZA0hfDtreCNHxsGwVH Bj0Q== X-Gm-Message-State: AMCzsaXMrU5qFpx0Xi5oAp7gN9MjF4iik2Na+bNrn04lrPyvaBHphBx7 B8sLQye49gX3lcU4Q4hOBihnmIY5ZP2Ft5bD9FhFEp/5 X-Google-Smtp-Source: ABhQp+Tuifhyd3YspZOOkLLw/9xZjCXpwWnan3YiYVWSdgbIuV4yP3HIafHkRbYgATc19dQMO1YH62AaL3/KpHLXhdw= X-Received: by 10.31.11.14 with SMTP id 14mr1357460vkl.69.1508429433478; Thu, 19 Oct 2017 09:10:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.10.147 with HTTP; Thu, 19 Oct 2017 09:10:12 -0700 (PDT) From: Jean Baro Date: Thu, 19 Oct 2017 14:10:12 -0200 Message-ID: Subject: Low priority batch insert To: pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary="001a11458efa8d24b1055be89822" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --001a11458efa8d24b1055be89822 Content-Type: text/plain; charset="UTF-8" Hi there, That's my first question in this mailing list! :) Is it possible (node.js connecting to PG 9.6 on RDS) to set a lower priority to a connection so that that particular process (BATCH INSERT) would have a low impact on other running processes on PG, like live queries and single inserts/updates? I would like the batch insert to complete as soon as possible, but at the same time keep individual queries and inserts running on maximum speed. *SINGLE SELECTS (HIGH PRIORITY)* *SINGLE INSERTS/UPDATES (HIGH PRIORITY)* BATCH INSERT (LOW PRIORITY) BATCH SELECT (LOW PRIORITY) Is that a good idea? Is this feasible with Node.js + PG? Thanks --001a11458efa8d24b1055be89822 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi there,

That's my first question = in this mailing list! :)

Is it possible (node.= js connecting to PG 9.6 on RDS) to set a lower priority to a connection so = that that particular process (BATCH INSERT) would have a low impact on othe= r running processes on PG, like live queries and single inserts/updates?

I would like the batch insert to complete as soon as= possible, but at the same time keep individual queries and inserts running= on maximum speed.
SINGLE SELECTS (HIGH PRIORITY)
SINGLE INSERTS/UPDAT= ES (HIGH PRIORITY)
BATCH INSERT (LOW PRIORITY)
BATCH SELECT (LOW PRIORITY)

<= span style=3D"background-color:rgb(255,0,0)">

Is that a good idea? Is this= feasible with Node.js + PG?<= font color=3D"#ffffff">

Thanks
--001a11458efa8d24b1055be89822--