Re: Long running INSERT+SELECT query

From: Steven Lembark <lembark(at)wrkhors(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Cc: lembark(at)wrkhors(dot)com
Subject: Re: Long running INSERT+SELECT query
Date: 2018-04-27 14:30:27
Message-ID: 20180427093027.6959987e@wrkhors.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 26 Apr 2018 23:32:33 +0300
Vitaliy Garnashevich <vgarnashevich(at)gmail(dot)com> wrote:

> The aggregated table has hundreds of millions of rows, and the query
> runs for many hours (which is one of the reasons why it's better not
> to fail). I really doubt that row level locking would work. That
> would be a lot of RAM just to hold all the locks.

All the more reason to use temp tables.

--
Steven Lembark 1505 National Ave
Workhorse Computing Rockford, IL 61103
lembark(at)wrkhors(dot)com +1 888 359 3508

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2018-04-27 14:40:58 Re: Parameter passing in trigger function write in C
Previous Message Steven Lembark 2018-04-27 14:29:30 Re: Long running INSERT+SELECT query