From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: performance problem on big tables |
Date: | 2017-08-15 17:44:51 |
Message-ID: | CAFj8pRA1uNq96KYVR+NP_M3GfqqvuBOh-DmMuZAcYqCdtJ_LiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2017-08-15 18:13 GMT+02:00 Jeff Janes <jeff(dot)janes(at)gmail(dot)com>:
> On Tue, Aug 15, 2017 at 3:06 AM, Mariel Cherkassky <
> mariel(dot)cherkassky(at)gmail(dot)com> wrote:
>
>> Hi,
>> So I I run the cheks that jeff mentioned :
>> \copy (select * from oracle_remote_table) to /tmp/tmp with binary - 1
>> hour and 35 minutes
>> \copy local_postresql_table from /tmp/tmp with binary - Didnt run because
>> the remote oracle database is currently under maintenance work.
>>
>
> The "\copy...from" doesn't depend on oracle, it would be only depend on
> local file system (/tmp/tmp), provided that the "\copy...to" finished.
> Anyway, given the length of time it took, I think you can conclude the
> bottleneck is in oracle_fdw itself, or in Oracle, or the network.
>
dumping from Oracle is not fast - I seen it when oracle_fdw or ora2pg cases.
Regards
Pavel
>
> Cheers,
>
> Jeff
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mariel Cherkassky | 2017-08-16 12:26:29 | Re: performance problem on big tables |
Previous Message | Scott Marlowe | 2017-08-15 17:14:14 | Re: performance problem on big tables |