Sergei Shelukhin escribió:
> * What other non-default configuration settings do you have?
> I played w/shared buffers, setting them between 16k and 32k,~ 24k
> seems to be the best but the difference is minimal. The work_mem
> setting is 256kb, and I increased effective cache size to ~700Mb (~35%
Hi. Sorry for being a bit emotional, I was pretty constructive in my
earlier posts (the earlier, the more constructive if you care to
search) but I am progressively getting pissed off :(
Thanks for the initial tip, running ANALYZE w/o vacuum is faster. Are
frequent vacuums even necessary if there
errr... workmem is 256Mb of course, and 5m for explain analyze costs.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Sergei Shelukhin wrote:
This is my first (and, by the love of the God, last) project w/pgsql
and everything but the simplest selects is so slow I want to cry.
This is especially bad with vacuum analyze - it takes several hours
for a database of mere 15 Gb on a fast double-core server w/2Gb of RAM
On Sun, 17 Jun 2007, Sergei Shelukhin wrote:
Is there any way to speed up ANALYZE? Without it all the queries run
so slow that I want to cry after a couple of hours of operation and
with it system has to go down for hours per day and that is
unacceptable.
I've found I cry a lot less if I actua
In response to Sergei Shelukhin <[EMAIL PROTECTED]>:
> This is my first (and, by the love of the God, last) project w/pgsql
One has to ask, are you actually looking for help, or trolling?
If you honestly want help, I would suggest you work on your communication
skills first. If you're a troll,
On Jun 17, 2007, at 2:15 PM, Sergei Shelukhin wrote:
This is my first (and, by the love of the God, last) project w/pgsql
and everything but the simplest selects is so slow I want to cry.
This is especially bad with vacuum analyze - it takes several hours
for a database of mere 15 Gb on a fast do
Sergei Shelukhin escribió:
> The same database running on mysql on basically the same server used
> to run optimize table on every table every half an hour without any
> problem, I am actually pondering scraping half the work on the
> conversion and stuff and going back to mysql but I wonder if th
On Jun 17, 2007, at 2:15 PM, Sergei Shelukhin wrote:
This is my first (and, by the love of the God, last) project w/pgsql
and everything but the simplest selects is so slow I want to cry.
This is especially bad with vacuum analyze - it takes several hours
for a database of mere 15 Gb on a fast
This is my first (and, by the love of the God, last) project w/pgsql
and everything but the simplest selects is so slow I want to cry.
This is especially bad with vacuum analyze - it takes several hours
for a database of mere 15 Gb on a fast double-core server w/2Gb of RAM
and virtually no workload
Sergei Shelukhin <[EMAIL PROTECTED]> wrote:
> This is my first (and, by the love of the God, last) project w/pgsql
> and everything but the simplest selects is so slow I want to cry.
Please post an example query and its EXPLAIN ANALYZE output. The
pgsql-performance mailing list is a good place to
A long time ago, in a galaxy far, far away, Sergei Shelukhin <[EMAIL
PROTECTED]> wrote:
> This is my first (and, by the love of the God, last) project w/pgsql
> and everything but the simplest selects is so slow I want to cry.
> This is especially bad with vacuum analyze - it takes several hours
>
12 matches
Mail list logo
