Hello,

 6000ms is the time which I have to wait until query finishes. The pgadmin
shows time 6000ms..

L

> On Thu, 2006-10-05 at 02:27 +0300, Lukas wrote:
>> Hello,
>>
>>  Well it is actual query run time.. I do not now why it is takes so long
>> bu tit takes..
>
> Where are you getting the measurement that tells you that the query is
> taking 6000ms?  Is it from your application?  EXPLAIN ANALYZE runs the
> actual query, and reports the time back.  The statement below clearly
> shows
>
> Total runtime: 0.416 ms"
>
> That's how long the query took.
>
> Brad.
>
>
>> > On Wednesday 04 October 2006 14:56, Lukas wrote:
>> >> Hello,
>> >>
>> >>  We are running 5 servers with postgresql 8.1 and Slony 1.2.0. Our
>> >> servers
>> >> are fast enough, like 3.0 Gaz Xeon, with 2GB of RAM and 320 SCSI
>> disks.
>> >>  After putting two sets with 19 tables to replication our master
>> >> database
>> >> speed went down. With the selects everything is ok, but inserts are
>> >> taking terrible log time, for example insert to the table with 5
>> columns
>> >> and total 70 rows only takes up to 6000ms:
>> >> insert into padalinys_teises (tk_objektas, tk_personalas,
>> tk_padalinys)
>> >> VALUES (1,10,0)
>> >>
>> >> There is explain analyse output:
>> >>
>> >> explain analyse insert into padalinys_teises (tk_objektas,
>> >> tk_personalas,
>> >> tk_padalinys) VALUES (1,10,0);
>> >>
>> >> "Result  (cost=0.00..0.01 rows=1 width=0) (actual time=0.021..0.022
>> >> rows=1
>> >> loops=1)"
>> >> "Trigger for constraint fk_teises_klubuose_padalinys: time=0.055
>> >> calls=1"
>> >> "Trigger for constraint teises_klubuose_tk_personalas_fkey:
>> time=0.053
>> >> calls=1"
>> >> "Trigger _replikiukas_logtrigger_3: time=0.140 calls=1"
>> >> "Total runtime: 0.416 ms"
>> >
>> > I'm not sure where you are getting 6000ms from, this explain clearly
>> shows
>> > less than 1/2 millisecond
>> >
>> >
>> >
>> >>
>> >> Is it normal? is it possible to do something about it?
>> >>
>> >> thx for any info
>> >>
>> >> Lukas
>> >
>> > --
>> > This message has been scanned for viruses and
>> > dangerous content, and is believed to be clean.
>> >
>> >
>>
>>
>>
>
>
> --
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content, and is believed to be clean.