| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mats Julian Olsen <mats(at)duneanalytics(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, wilhelm(at)duneanalytics(dot)com |
| Subject: | Re: postgres_fdw insert extremely slow |
| Date: | 2020-11-25 17:12:25 |
| Message-ID: | 494596.1606324345@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mats Julian Olsen <mats(at)duneanalytics(dot)com> writes:
> On 25.11.2020 17:58, Tom Lane wrote:
>> ... Have you tried looking into pg_locks on the
>> remote server while this query is running?
> Thanks Tom, I'll try to spin up a regular Postgres instance on both rds
> and ec2 and see if that helps. As for the locks, I can not see any
> blocked activity on the remote server while the query runs.
Another place to check is pg_stat_activity, specifically wait_event_type
and wait_event.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-11-25 17:13:16 | Re: INSERT Trigger to check for existing records : Does this do what I hope it is doing? |
| Previous Message | Bruce Momjian | 2020-11-25 17:09:29 | Re: Performance hit if I create multiple DBs on same instance |