Hi,
The effect is the same even if I redirect the output to file with the -o
switch.
At the beginning 200 KB/sec, at 1.5 MB the speed is less than 20 KB/sec.
Best Regards,
Otto
----- Original Message -----
From: "Havasvölgyi Ottó" <h.otto@freemail.hu>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <pgsql-general@postgresql.org>
Sent: Tuesday, August 02, 2005 11:24 AM
Subject: Re: [GENERAL] feeding big script to psql
> Tom,
>
> Thanks for the suggestion. I have just applied both switch , -f (I have
> applied this in the previous case too) and -n, but it becomes slow again.
> At the beginning it reads about 300 KB a second, and when it has read 1.5
> MB, it reads only about 10 KB a second, it slows down gradually. Maybe
> others should also try this scenario. Can I help anything?
>
> Best Regards,
> Otto
>
>
> ----- Original Message -----
> From: "Tom Lane" <tgl@sss.pgh.pa.us>
> To: "Havasvölgyi Ottó" <h.otto@freemail.hu>
> Cc: <pgsql-general@postgresql.org>
> Sent: Tuesday, August 02, 2005 3:54 AM
> Subject: Re: [GENERAL] feeding big script to psql
>
>
>> =?ISO-8859-1?Q?Havasv=F6lgyi_Ott=F3?= <h.otto@freemail.hu> writes:
>>> I know it would be faster with COPY, but this is extremly slow, and the
>>> bottleneck is psql.
>>> What is the problem?
>>
>> Hmm, does the Windows port have readline support, and if so does adding
>> the "-n" switch to the psql invocation fix the problem? Or you could
>> try feeding the script with -f switch or \i rather than "psql <script".
>> Readline adds a fair amount of overhead, which is completely invisible
>> at human typing speeds but can be annoying when reading scripts.
>>
>> regards, tom lane
>>
>>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
