Re: postgres 9.6: insert into select finishes only in pgadmin not psql

From: Corey Taylor <corey(dot)taylor(dot)fl(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: postgres 9.6: insert into select finishes only in pgadmin not psql
Date: 2019-09-23 21:34:57
Message-ID: CADBz38788sE8G54daHmfVYkaMhYTEdFyd--BtdF=2BOJGuj8Gw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Sep 23, 2019 at 4:31 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> Hmm, are there triggers on wss_entries that are UPDATEing/DELETEing
> entries elsewhere?
>

No, that table is pretty much stand-alone. What we're seeing here is most
likely caused by the initial copy of the legacy db tables.

This happens when creating the local test db which I do right before the
tests. I can avoid the issue if I monitor top and wait for the analyze to
complete on all the related tables.

corey

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-09-23 21:50:55 Re: postgres 9.6: insert into select finishes only in pgadmin not psql
Previous Message Adrian Klaver 2019-09-23 21:31:27 Re: postgres 9.6: insert into select finishes only in pgadmin not psql