So guys, lot of thank you for all of the explanation and ideas!
Jeff Janes wrote:
> What happens if the database has a hiccup and can't accept records for
> a few seconds or minutes?
Craig Ringer wrote:
> If you really need absolutely maximum insert performance, you should
> just use a flat fil
Hi Radhya,
Make multiple EXPLAIN requests, and add them up in your application, I
guess?
--
Robins
Sr. PGDBA
Comodo India
On 10/22/2011 06:41 AM, Radhya sahal wrote:
such as
explain (q1,q2,q3)..i want the total cost for all queries in the
workload using one explain ,,??
smime.p7s
Des
Robins Tharakan writes:
> Hi Radhya,
> Make multiple EXPLAIN requests, and add them up in your application, I
> guess?
Or maybe contrib/auto_explain would help.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make chan
* Stefan Keller (sfkel...@gmail.com) wrote:
> Adding more memory (say to total of 32 GB) would only postpone the problem.
Erm, seems like you're jumping to conclusions here...
> First time the query lasts about 10 time longer (~ 1010 ms) - but I'd
> like to get better results already in the first
Hi Stephen
Thanks for your answer and hints.
2011/10/24 Stephen Frost wrote:
> * Stefan Keller (sfkel...@gmail.com) wrote:
>> Adding more memory (say to total of 32 GB) would only postpone the problem.
> Erm, seems like you're jumping to conclusions here...
Sorry. I actually only wanted to repo
* Stefan Keller (sfkel...@gmail.com) wrote:
> >> Adding more memory (say to total of 32 GB) would only postpone the problem.
> > Erm, seems like you're jumping to conclusions here...
>
> Sorry. I actually only wanted to report here what's special in my
> postgresql.conf.
My comment was referring
