| 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 |
| Subject: | Re: postgres_fdw insert extremely slow |
| Date: | 2020-11-25 16:58:29 |
| Message-ID: | 493978.1606323509@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:
>> Postgres version(s)?
> x: Aurora PostgreSQL 11.7 on x86_64-pc-linux-gnu, compiled by gcc (GCC)
> 4.9.3, 64-bit (RDS)
> y: PostgreSQL 12.2 (Ubuntu 12.2-2.pgdg19.10+1) on x86_64-pc-linux-gnu,
> compiled by gcc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008, 64-bit (GCP)
Hmm, I wonder if Aurora could be doing something funny here?
Anyway, to answer your question, no that's not the expected level of
performance. postgres_fdw is certainly not inexpensive compared to
local table access, but I'd still think inserts should take only a
small number of milliseconds. It seems like something must be
blocking the query. Have you tried looking into pg_locks on the
remote server while this query is running?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mats Julian Olsen | 2020-11-25 17:01:57 | Re: postgres_fdw insert extremely slow |
| Previous Message | Adrian Klaver | 2020-11-25 16:57:49 | Re: postgres_fdw insert extremely slow |