Em qui, 13 de set de 2018 às 19:53, David G. Johnston <
david.g.johns...@gmail.com> escreveu:
> On Thu, Sep 13, 2018 at 3:30 PM, Neto pr wrote:
>
>> The problem is that using the explain analyze I have to wait for
>> the query to execute.
>> I would like to estim
waiting for the query to
be executed?
Best regards
Neto
> thanks,
>
> Vijay
>
>
>
> *From: *Johnes Castro
> *Date: *Friday, September 14, 2018 at 3:12 AM
> *To: *Neto pr , PostgreSQL General <
> pgsql-gene...@postgresql.org>
> *Subject: *[External] RE: Es
Dear all,
Only a doubt.
The Explain command only estimates the cost of execution of a
query, and does not estimate time for execution.
I would like know if exists some way to estimate the time, without running
the query?
Best Regards
[]`s Neto
Dear,
2018-05-05 9:57 GMT-07:00 Adrian Klaver :
> On 05/05/2018 06:26 AM, Neto pr wrote:
>
>> Dear all
>>
>> Could you help me understand these two execution plans for the same query
>> (query 3 benchmark TPCH www.tpc.org/tpch <http://www.tpc.org/tpc
Further information is These plans were generated by the EXPLAIN ANALYZE
command, and the time of plan 1 (Postgresql 10.1 ) was 4.7 minutes and
plan 2 (postgresql 9.5 changed) was 2.95 minutes.
2018-05-05 6:26 GMT-07:00 Neto pr :
> Dear all
>
> Could you help me understand these two
Dear all
Could you help me understand these two execution plans for the same query
(query 3 benchmark TPCH www.tpc.org/tpch), executed in two different
environments of Postgresql, as described below:
Execution Plan 1:
- https://explain.depesz.com/s/Ughh
- Postgresql version 10.1 (default) with ind
2018-01-21 13:53 GMT-08:00 Peter J. Holzer :
> On 2018-01-21 12:45:54 -0800, Neto pr wrote:
> > I need to know the actual execution time of a query, but considering
> that the
> > data is already cached. I also need to make sure that cached data from
> other
> > querie
Hi all,
I need to know the actual execution time of a query, but considering that
the data is already cached. I also need to make sure that cached data from
other queries is cleared.
I believe that in order to know the real time of a query it will be
necessary to "warm up" the data to be inserted i
2018-01-16 8:50 GMT-08:00 Michael Loftis :
>
> On Tue, Jan 16, 2018 at 08:02 Scott Marlowe
> wrote:
>
>> On Tue, Jan 16, 2018 at 7:47 AM, Neto pr wrote:
>> > Hi all
>> >
>> > Sorry, but I'm not sure that this doubt is appropriate for this list
Hi all
Sorry, but I'm not sure that this doubt is appropriate for this list, but I
do need to prepare the file system of an SSD disk in a way that pointed me
to, which would be a way optimized SSD
to work. I have a disk: SSD: Samsung 500 GB SATA III 6Gb/s - Model: 850 Evo
http://www.samsung.com/s
ock size was set by default
when I formatted the drive. I use Debian 64bits version 8, and all disks
are with ext4 file system. What size block do you suggest for SSD and HDD?
Neto
> -- Původní e-mail --
> Od: Merlin Moncure
> Komu: Neto pr
> Datum: 15. 1. 2018 20:
Dear Merlin
2018-01-15 11:16 GMT-08:00 Merlin Moncure :
> On Mon, Jan 15, 2018 at 7:38 AM, Neto pr wrote:
> > Hello all,
> > Someone help me analyze the two execution plans below (Explain ANALYZE
> > used), is the query 9 of TPC-H benchmark [1].
> > I'm using tw
2018-01-15 9:13 GMT-08:00 Vick Khera :
> Try random page cost 1.1. Way back when I started using SSD we had a
> discussion here and came to the conclusion that it should be ever so
> slightly higher than sequential page cost.
>
>
Very good tip, I'm running the query with random_page_cost = 1.1, bu
Hello all,
Someone help me analyze the two execution plans below (Explain ANALYZE
used), is the query 9 of TPC-H benchmark [1].
I'm using two servers HP Intel Xeon 2.8GHz/4-core - Memory 8GB. O.S.
Debian8, using EXT4 filesystem.
Server 1
- HDD SAS 15 Krpm - 320 GB (Location where O.S. Debian and
-03:00 Neto pr :
> Only complementing
> I use postgresql version 10.
> However the postgresql.conf file has standard settings.
> My server is a 2.8 GHz Xeon (4 core) and SSDs disc.
>
> 2017-11-22 21:12 GMT-03:00 Neto pr :
>
>> Dear all,
>> when executing a query, it
Only complementing
I use postgresql version 10.
However the postgresql.conf file has standard settings.
My server is a 2.8 GHz Xeon (4 core) and SSDs disc.
2017-11-22 21:12 GMT-03:00 Neto pr :
> Dear all,
> when executing a query, it causes the database to close the connection.
> See
Dear all,
when executing a query, it causes the database to close the connection.
See the error reported by the SQL TOOL DBEAVER tool:
- DBEAVER SQL tool-
An I / O error occurred while sending to the backend.
java.io.EOFException:
---
17 matches
Mail list logo
