| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: performance problem on big tables |
| Date: | 2017-08-14 16:39:06 |
| Message-ID: | CAMkU=1zsJd4eKhDa0MLzDxUzPnJ=0YaPK01YMx3-izm=gwiJfA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Aug 14, 2017 at 6:24 AM, Mariel Cherkassky <
mariel(dot)cherkassky(at)gmail(dot)com> wrote:
> I have performance issues with two big tables. Those tables are located on
> an oracle remote database. I'm running the quert : insert into
> local_postgresql_table select * from oracle_remote_table.
>
> The first table has 45M records and its size is 23G. The import of the
> data from the oracle remote database is taking 1 hour and 38 minutes.
>
To investigate this, I'd decouple the two steps and see how long each one
takes:
\copy (select * from oracle_remote_table) to /tmp/tmp with binary
\copy local_postresql_table from /tmp/tmp with binary
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Finzel | 2017-08-14 19:53:48 | Odd sudden performance degradation related to temp object churn |
| Previous Message | Rick Otten | 2017-08-14 15:45:01 | Re: performance problem on big tables |