MIME-Version: 1.0
In-Reply-To: 
 <CA+fQeemNM8s9Y0_WKJ+rKStR9iePV3yfW+Rh6nhPUyGcJf3+hg@mail.gmail.com>
References: 
 <CA+fQeemNM8s9Y0_WKJ+rKStR9iePV3yfW+Rh6nhPUyGcJf3+hg@mail.gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
Date: Fri, 20 Oct 2017 07:54:16 +0900
Message-ID: 
 <CAB7nPqTJD79=tnTQb+MW2Y3ERKCR9WiShTNLgkrs18bJeTxs9A@mail.gmail.com>
Subject: Re: Low priority batch insert
To: Jean Baro <jfbaro@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-performance@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On Fri, Oct 20, 2017 at 1:10 AM, Jean Baro <jfbaro@gmail.com> wrote:
> That's my first question in this mailing list! :)

Welcome!

> 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?
>
> Is that a good idea? Is this feasible with Node.js + PG?

The server could be changed so as backend processes use setpriority
and getpriority using a GUC parameter, and you could leverage priority
of processes using that. The good news is that this can be done as a
module, see an example from Fujii Masao's pg_cheat_funcs that caught
my attention actually yesterday:
https://github.com/MasaoFujii/pg_cheat_funcs/commit/a39ec1549e2af72bf101da5075c4e12d079f7c5b
The bad news is that you are on RDS, so vendor locking is preventing
you from loading any custom modules.
-- 
Michael


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance