On 02/07/2003 21:04 Matthew Hixson wrote:
We currently have a public website that is serving customers, or at
least trying to. This machine is underpowered but we are going to be
upgrading soon. In the meantime we need to keep the current site alive.
We are running a Java application server.
> CREATE VIEW foo AS {complex_slow_query};
>
> SET random_page_cost = 1.5; EXPLAIN ANALYZE SELECT * FROM foo;
>
> Note the time taken. Repeat a few times to get the average.
You pulled everything off disk and tossed it into memory with the first
run so the results will NOT match your normal situ
What are the odds of going through and revamping some of the tunables
in postgresql.conf for the 7.4 release? I was just working with
someone on IRC and on their 7800 RPM IDE drives, their
random_page_cost was ideally suited to be 0.32: a far cry from 4.
Doing so has been a win across the board an
On Thu, 2003-07-03 at 19:05, Sean Chittenden wrote:
> What are the odds of going through and revamping some of the tunables
> in postgresql.conf for the 7.4 release? I was just working with
> someone on IRC and on their 7800 RPM IDE drives, their
> random_page_cost was ideally suited to be 0.32: a
On Thu, 3 Jul 2003, Sean Chittenden wrote:
> What are the odds of going through and revamping some of the tunables
> in postgresql.conf for the 7.4 release? I was just working with
> someone on IRC and on their 7800 RPM IDE drives, their
> random_page_cost was ideally suited to be 0.32: a far cry
I don't have much to add because I'm pretty new to Postgres and have been
soliciting advice here recently, but I totally agree with everything you
said. I don't mind if it's in the postgres.conf file or in a faq that is
easy to find, I just would like it to be in one place. A good example of
the
Hear, hear!
Well said Sean. I know that there has been disagreement about this in
the past (recommending settings, with some very good reasons), however
as a programmer/part-time DBA, something like this would be extremely
useful. Our company recently developed a web-based app for a client who
Sean Chittenden <[EMAIL PROTECTED]> writes:
> What are the odds of going through and revamping some of the tunables
> in postgresql.conf for the 7.4 release?
I was arguing awhile back for bumping the default shared_buffers up,
but the discussion trailed off with no real resolution.
> I was just w
I'm curious how many of the configuration values can be determined
automatically, or with the help of some script. It seem like there
could be some perl script in contrib that could help figure this out.
Possibly you are asked a bunch of questions and then the values are
computed based on tha
> > What are the odds of going through and revamping some of the
> > tunables in postgresql.conf for the 7.4 release? I was just
> > working with someone on IRC and on their 7800 RPM IDE drives,
> > their random_page_cost was ideally suited to be 0.32: a far cry
> > from 4. Doing so has been a wi
> I'm curious how many of the configuration values can be determined
> automatically, or with the help of some script. It seem like there
> could be some perl script in contrib that could help figure this out.
> Possibly you are asked a bunch of questions and then the values are
> computed ba
> > What are the odds of going through and revamping some of the
> > tunables in postgresql.conf for the 7.4 release? I was just
> > working with someone on IRC and on their 7800 RPM IDE drives,
> > their random_page_cost was ideally suited to be 0.32: a far cry
> > from 4.
>
> I find it very ver
> > What are the odds of going through and revamping some of the tunables
> > in postgresql.conf for the 7.4 release?
>
> I was arguing awhile back for bumping the default shared_buffers up,
> but the discussion trailed off with no real resolution.
>
> > I was just working with someone on IRC and
Sean Chittenden <[EMAIL PROTECTED]> writes:
> Getting the planner to pick
> using the index to filter out data inserted in the last 3 days over
> doing a seq scan... well, I don't know how you could do that without
> changing the random_page_cost.
This sounds a *whole* lot like a correlation issu
Sean, Tom, Rod, Michael, Brian, Ron:
I'm going to paste everything into one monumental response. So be prepared to
scroll.
Sean Asks:
> What are the odds of going through and revamping some of the tunables
> in postgresql.conf for the 7.4 release?
Poor. The time to do this would have been
Josh Berkus <[EMAIL PROTECTED]> writes:
> Kevin Brown and I followed that up by trying to build a downloadable public
> domain database that could be used for benchmarking. However, he got an FT
> job and I got distracted by prep for 7.4. So, a little help?
BTW, OSDL (Linus' new home ;-)) is s
Josh Berkus <[EMAIL PROTECTED]> writes:
> Sean Asks:
>> What are the odds of going through and revamping some of the tunables
>> in postgresql.conf for the 7.4 release?
> Poor. The time to do this would have been 3 weeks ago, when I
> announced that I was re-organizing them and that Bruce was c
17 matches
Mail list logo
