Executing "Select count(a.*) from (select ... from mytable join .. join ...
order by ) as a;"
Total query runtime: 454 ms.
1 row retrieved.
--
View this message in context:
http://postgresql.nabble.com/Copy-command-Faster-than-original-select-tp5836886p5837105.html
Sent from the Postgre
Let me change my question to this perhaps it would be clearer
why writing data result of select statment from PG server to file on disk
using copy statement is much faster than getting same data through PGAdmin
via libpg on the same PC on the same system on the same connection
(localhost) ?
--
"so bottle neck have to be some where between client and server"
that's what I need to know !
where is the bug to made this performance
"Can you try again but with EXPLAIN *ANALYZE* (not only EXPLAIN)?"
it's not a matter of plan problem I think, it's related to sending data
from server to client
fast as
Query returned successfully: 43602 rows affected, 1089 ms execution time.
--
View this message in context:
http://postgresql.nabble.com/Copy-command-Faster-than-original-select-tp5836886p5836902.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent
"this slowdown can be enforced by slow client (or slow network)."
As I said i made the tow test on the same machine as the server using
PGAdmin no network involved.
"pgAdmin is not terrible fast"
I also try the same query from my application using libpq I get same results
regards
--
View this
thanks,
but isn't copy use the same plan ???
any way this is the query play
"Sort (cost=15402.76..15511.77 rows=43602 width=184)"
" Output: "Sessions"."SesUser", "Vouchers"."VouID",
"Journals"."JurMuniment", "Journals"."JurRefID", "Journals"."JurDate",
"Vouchers"."VouJournal", "Vouchers"."VouM
