great,
thank you a lot Guillaume!
Cheers,
Boris
On 11/03/2011 12:20 PM, Guillaume Lelarge wrote:
On Thu, 2011-11-03 at 12:02 +0100, Guillaume Lelarge wrote:
On Thu, 2011-11-03 at 11:22 +0100, boris pezzatti wrote:
I tested after column types, and the colum that appears to create the
very
difference
probably has to do with me testing on a table with lots of columns,
many of type timestamp and inet which I assume are costlier to
convert. Boris, might that be the case with you also?
I'll repeat my tests with a smaller and simpler table later.
> The file is being writt
a variable
and storing all at once (or let say in chunks of 100 Mb) could solve the
problem ...
On 11/02/2011 09:10 AM, boris pezzatti wrote:
or maybe the retrieved data in RAM are somehow lazy bound ... ?
On 11/02/2011 08:58 AM, boris pezzatti wrote:
Thank you Fernando for reproducing
or maybe the retrieved data in RAM are somehow lazy bound ... ?
On 11/02/2011 08:58 AM, boris pezzatti wrote:
Thank you Fernando for reproducing this.
I suspect there must be some part of code in the
* for each row
* for each column
loops that result inefficient only on some machines or
ched if there were some parts that took much longer than others,
but failed to find one.
--
*Boris Pezzatti
Swiss Federal Research Institute WSL
*
Research unit Community Ecology
Team Insubric Ecosystems
via Belsoggiorno 22
CH-6500 Bellinzona
Switzerland phone direct ++41 91 821 52 32
p
retrieved separately and written to the file
location? Or is written first to a temporary location and then copied?
Maybe I'll have to start looking into the source code
Thanks anyway,
Boris
On 10/31/2011 12:54 PM, Francisco Leovey wrote:
I propose you output to a file located on the
No, actually it is on my machine ...
On 10/29/2011 11:01 PM, Francisco Leovey wrote:
Is the file where you write the query output located on the same
server as the DB?
*From:* boris pezzatti
*To:* Guillaume Lelarge
Does anyone have any proposition how I could further test where the
problem is. This is really a strange behaviour, that I noticed with
different versions of pgAdmin.
Could a firewall produce a difference when querying data visually or for
a write to file? (should not ...)
Thank you,
Boris
t 10 MB in 45 minutes).
Am I doing something wrong?
Are there some parameters to set?
This happens with the version 1.14 of pgAdmin, but used also to be very
slow with the previous versions (2-3 years ago).
OS : Archlinux (but had the same problem 1-2 years ago with ubuntu)
Thank you ,
Boris
On 09/20/2011 03:13 AM, Guillaume Lelarge wrote:
On Mon, 2011-09-19 at 21:27 -0400, boris wrote:
hi all,
I guess , this is very basic question, but I don't see any options to
fix it.
why when I do select , strings in "data output" are in quotes and
parenthesis?
How do I turn
hi all,
I guess , this is very basic question, but I don't see any options to
fix it.
why when I do select , strings in "data output" are in quotes and
parenthesis?
How do I turn it off? I would like to see plain data...
thanks.
--
Sent via pgadmin-support mailing list (pgadmin-support@postg
11 matches
Mail list logo
