Postgres Pro
Downloads
Home   >   mailing lists

Thread: Re: [Performance] Daily Crash

Re: [Performance] Daily Crash

From
Aspire Something
Date:
Dear Catalin,


What I understand from ur post is,
1. U are using PHP for connection. what version ??? assuming u are on PHP
version >4.2.X
2. Ur Postgresql server is not tuned to handle loads.

What U can try is ......

1.Make sure  that ur PHP scripts close the connection when transaction is
complete (HOW??? see after pg_connect

U  see a pg_close function of PHP)
        a. Use pg_pconnect  and forget about pg_connect and pg_close
2. Increse the limit of connection to be made to PostgreSQL  this can be
done as said by Shridhar the default is 32
3. For God sake Upgrade to PostgreSQL 7.3.2 and PHP 4.3.1 you are missing a
lot with that old versions.



Regards,
V Kashyap

================================
Some people think it's holding on that makes one strong;
 sometimes  it's letting go.
================================

Re: [Performance] Daily Crash

From
"Catalin"
Date:
i have php 4.2.3
i use pg_pConnect and no pg_Close.

thanks for yours advices.
i will upgrade to postgresql 7.2.3 asap
and see if there are improvments !

thanks again !

Catalin

----- Original Message -----
From: Aspire Something
To: pgsql-performance@postgresql.org
Sent: Thursday, February 27, 2003 4:44 PM
Subject: Re: [PERFORM] [Performance] Daily Crash


Dear Catalin,


What I understand from ur post is,
1. U are using PHP for connection. what version ??? assuming u are on PHP
version >4.2.X
2. Ur Postgresql server is not tuned to handle loads.

What U can try is ......

1.Make sure  that ur PHP scripts close the connection when transaction is
complete (HOW??? see after pg_connect

U  see a pg_close function of PHP)
        a. Use pg_pconnect  and forget about pg_connect and pg_close
2. Increse the limit of connection to be made to PostgreSQL  this can be
done as said by Shridhar the default is 32
3. For God sake Upgrade to PostgreSQL 7.3.2 and PHP 4.3.1 you are missing a
lot with that old versions.



Regards,
V Kashyap

================================
Some people think it's holding on that makes one strong;
 sometimes  it's letting go.
================================



---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Re: [Performance] Daily Crash

From
Josh Berkus
Date:
Catalin,

> thanks for yours advices.
> i will upgrade to postgresql 7.2.3 asap
> and see if there are improvments !

Um, that's 7.2.4.   7.2.3 has a couple of bugs in it.

Also, you are going to have to edit your postgresql.conf file per the
suggestions already made on this list.

--
Josh Berkus
Aglio Database Solutions
San Francisco

Re: [Performance] Daily Crash

From
"philip johnson"
Date:
pgsql-performance-owner@postgresql.org wrote:
> i have php 4.2.3
> i use pg_pConnect and no pg_Close.
>
> thanks for yours advices.
> i will upgrade to postgresql 7.2.3 asap
> and see if there are improvments !
>
> thanks again !
>
> Catalin
>
> ----- Original Message -----
> From: Aspire Something
> To: pgsql-performance@postgresql.org
> Sent: Thursday, February 27, 2003 4:44 PM
> Subject: Re: [PERFORM] [Performance] Daily Crash
>
>
> Dear Catalin,
>
>
> What I understand from ur post is,
> 1. U are using PHP for connection. what version ??? assuming u are on
> PHP version >4.2.X
> 2. Ur Postgresql server is not tuned to handle loads.
>
> What U can try is ......
>
> 1.Make sure  that ur PHP scripts close the connection when
> transaction is complete (HOW??? see after pg_connect
>
> U  see a pg_close function of PHP)
>         a. Use pg_pconnect  and forget about pg_connect and pg_close
> 2. Increse the limit of connection to be made to PostgreSQL  this can
> be done as said by Shridhar the default is 32
> 3. For God sake Upgrade to PostgreSQL 7.3.2 and PHP 4.3.1 you are
> missing a lot with that old versions.
>
>
>
> Regards,
> V Kashyap
>
> ================================
> Some people think it's holding on that makes one strong;
>  sometimes  it's letting go.
> ================================
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 2: you can get off all
>     lists at once with the unregister command (send "unregister
> YourEmailAddressHere" to majordomo@postgresql.org)
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 5: Have you checked our
> extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

you can use no persistent link to database
see in php.ini

pgsql.allow_persistent = Off

Re: [Performance] Daily Crash

From
"Catalin"
Date:
how often should i run VACUUM to keep the thing tunned ?

Catalin

----- Original Message -----
From: philip johnson
To: Catalin ; pgsql-performance@postgresql.org
Sent: Thursday, February 27, 2003 8:51 PM
Subject: RE: [PERFORM] [Performance] Daily Crash


pgsql-performance-owner@postgresql.org wrote:
> i have php 4.2.3
> i use pg_pConnect and no pg_Close.
>
> thanks for yours advices.
> i will upgrade to postgresql 7.2.3 asap
> and see if there are improvments !
>
> thanks again !
>
> Catalin
>
> ----- Original Message -----
> From: Aspire Something
> To: pgsql-performance@postgresql.org
> Sent: Thursday, February 27, 2003 4:44 PM
> Subject: Re: [PERFORM] [Performance] Daily Crash
>
>
> Dear Catalin,
>
>
> What I understand from ur post is,
> 1. U are using PHP for connection. what version ??? assuming u are on
> PHP version >4.2.X
> 2. Ur Postgresql server is not tuned to handle loads.
>
> What U can try is ......
>
> 1.Make sure  that ur PHP scripts close the connection when
> transaction is complete (HOW??? see after pg_connect
>
> U  see a pg_close function of PHP)
>         a. Use pg_pconnect  and forget about pg_connect and pg_close
> 2. Increse the limit of connection to be made to PostgreSQL  this can
> be done as said by Shridhar the default is 32
> 3. For God sake Upgrade to PostgreSQL 7.3.2 and PHP 4.3.1 you are
> missing a lot with that old versions.
>
>
>
> Regards,
> V Kashyap
>
> ================================
> Some people think it's holding on that makes one strong;
>  sometimes  it's letting go.
> ================================
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 2: you can get off all
>     lists at once with the unregister command (send "unregister
> YourEmailAddressHere" to majordomo@postgresql.org)
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 5: Have you checked our
> extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

you can use no persistent link to database
see in php.ini

pgsql.allow_persistent = Off

Re: [Performance] Daily Crash

From
"Catalin"
Date:
so i did the server upgrade to postgresql 7.3.2
and tunned it like you ppl said.

it works great.
plus my DB on postgresql 7.0 had 640 MB, including indexes, etc (files)
now it has only 140MB.
this is much better !

thank you for your help !

Catalin

----- Original Message -----
From: Catalin
To: pgsql-performance@postgresql.org
Sent: Thursday, February 27, 2003 10:19 PM
Subject: Re: [PERFORM] [Performance] Daily Crash


how often should i run VACUUM to keep the thing tunned ?

Catalin

----- Original Message -----
From: philip johnson
To: Catalin ; pgsql-performance@postgresql.org
Sent: Thursday, February 27, 2003 8:51 PM
Subject: RE: [PERFORM] [Performance] Daily Crash


pgsql-performance-owner@postgresql.org wrote:
> i have php 4.2.3
> i use pg_pConnect and no pg_Close.
>
> thanks for yours advices.
> i will upgrade to postgresql 7.2.3 asap
> and see if there are improvments !
>
> thanks again !
>
> Catalin
>
> ----- Original Message -----
> From: Aspire Something
> To: pgsql-performance@postgresql.org
> Sent: Thursday, February 27, 2003 4:44 PM
> Subject: Re: [PERFORM] [Performance] Daily Crash
>
>
> Dear Catalin,
>
>
> What I understand from ur post is,
> 1. U are using PHP for connection. what version ??? assuming u are on
> PHP version >4.2.X
> 2. Ur Postgresql server is not tuned to handle loads.
>
> What U can try is ......
>
> 1.Make sure  that ur PHP scripts close the connection when
> transaction is complete (HOW??? see after pg_connect
>
> U  see a pg_close function of PHP)
>         a. Use pg_pconnect  and forget about pg_connect and pg_close
> 2. Increse the limit of connection to be made to PostgreSQL  this can
> be done as said by Shridhar the default is 32
> 3. For God sake Upgrade to PostgreSQL 7.3.2 and PHP 4.3.1 you are
> missing a lot with that old versions.
>
>
>
> Regards,
> V Kashyap
>
> ================================
> Some people think it's holding on that makes one strong;
>  sometimes  it's letting go.
> ================================
>
>
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 2: you can get off all
>     lists at once with the unregister command (send "unregister
> YourEmailAddressHere" to majordomo@postgresql.org)
>
> ---------------------------(end of
> broadcast)--------------------------- TIP 5: Have you checked our
> extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html

you can use no persistent link to database
see in php.ini

pgsql.allow_persistent = Off

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)