Re: [PERFORM] High Processor consumption

2003-11-18 Thread Shridhar Daithankar
Benjamin Bostow wrote: I am running RH 7.3 running Apache 1.3.27-2 and PostgreSQL 7.2.3-5.73. When having 100+ users connected to my server I notice that postmaster consumes up wards of 90% of the processor and I hardly am higher than 10% idle. I did notice that when I kill apache and postmaster t

Re: [PERFORM] More detail on settings for pgavd?

2003-11-18 Thread Shridhar Daithankar
Josh Berkus wrote: Shridhar, I was looking at the -V/-v and -A/-a settings in pgavd, and really don't understand how the calculation works. According to the readme, if I set -v to 1000 and -V to 2 (the defaults) for a table with 10,000 rows, pgavd would only vacuum after 21,000 rows had been

[PERFORM] problem with select count(*) ..

2003-11-18 Thread Rajesh Kumar Mallah
Ever Since i upgraded to 7.4RC2 i am facing problem with select count(*) . In 7.3 the problem was not there select count(*) from data_bank.profiles used to return almost instantly , but in 7.4 explain analyze SELECT count(*) from data_bank.profiles;

[PERFORM] High Processor consumption

2003-11-18 Thread Benjamin Bostow
I am running RH 7.3 running Apache 1.3.27-2 and PostgreSQL 7.2.3-5.73. When having 100+ users connected to my server I notice that postmaster consumes up wards of 90% of the processor and I hardly am higher than 10% idle. I did notice that when I kill apache and postmaster that my idle processor p

[PERFORM] More detail on settings for pgavd?

2003-11-18 Thread Josh Berkus
Shridhar, I was looking at the -V/-v and -A/-a settings in pgavd, and really don't understand how the calculation works. According to the readme, if I set -v to 1000 and -V to 2 (the defaults) for a table with 10,000 rows, pgavd would only vacuum after 21,000 rows had been updated. This see

Re: [PERFORM] Join on incompatible types

2003-11-18 Thread Laurent Martelli
> "Shridhar" == Shridhar Daithankar <[EMAIL PROTECTED]> writes: Shridhar> Laurent Martelli wrote: [...] >> Should I understand that a join on incompatible types (such as >> integer and varchar) may lead to bad performances ? Shridhar> Conversely, you should enforce strict type compa

Re: [PERFORM] duration logging setting in 7.4

2003-11-18 Thread Bruce Momjian
Wow, that is strange. If you don't use syslog, do you see the proper output? If you turn on log_statement, do you see the statements? --- Ryszard Lach wrote: > On Mon, Nov 17, 2003 at 09:37:07PM -0500, Bruce Momjian wrote:

Re: [PERFORM] Join on incompatible types

2003-11-18 Thread Shridhar Daithankar
Laurent Martelli wrote: "scott" == scott marlowe <[EMAIL PROTECTED]> writes: [...] scott> Note here: scott> Merge Join (cost=1788.68..4735.71 rows=1 width=85) (actual scott> time=597.540..1340.526 rows=20153 loops=1) Merge Cond: scott> ("outer".id = "inner".id) scott> This estimate i

[PERFORM] Join on incompatible types

2003-11-18 Thread Laurent Martelli
> "scott" == scott marlowe <[EMAIL PROTECTED]> writes: [...] scott> Note here: scott> Merge Join (cost=1788.68..4735.71 rows=1 width=85) (actual scott> time=597.540..1340.526 rows=20153 loops=1) Merge Cond: scott> ("outer".id = "inner".id) scott> This estimate is WAY off. Are bot

Re: [PERFORM] duration logging setting in 7.4

2003-11-18 Thread Ryszard Lach
On Mon, Nov 17, 2003 at 09:37:07PM -0500, Bruce Momjian wrote: > Ryszard Lach wrote: > > > > Hi. > > > > I'm trying to set run-time environment in pgsql7.4 so, that it prints > > all statements with duration time, but I can't understand why setting > > log_min_duration_statement to '0' causes pri