Thread

1. stability problems

   Lars Maschke <lars@gmeiner.de> — 2001-03-28T10:42:04Z

   Hello Newsgroup
   
   I have stability problems with my Postgres 6.4 database. I am using PHP4.0.4
   and get access to the db. Sometimes when about 10-20 clients are using the
   website the postgres deamon shuts down and the message "no backend cache"
   appears. The processor ist at 60%-80% and about 10-15 postgres processes are
   on my linux machine. So what can i do ?
   
   My postgres-command is: /usr/lib/pgsql/bin/postmaster -B
   2048 -i -o -F -D/var/lib/pgsql
   
   Thanks
   Lars
   
   
   
   

2. Re: stability problems

   Marc G. Fournier <marc@atelier.acadiau.ca> — 2001-03-29T16:01:45Z

   "Lars Maschke" <lars@gmeiner.de> writes:
   
   >Hello Newsgroup
   
   >I have stability problems with my Postgres 6.4 database. I am using PHP4.0.4
   >and get access to the db. Sometimes when about 10-20 clients are using the
   >website the postgres deamon shuts down and the message "no backend cache"
   >appears. The processor ist at 60%-80% and about 10-15 postgres processes are
   >on my linux machine. So what can i do ?
   
   >My postgres-command is: /usr/lib/pgsql/bin/postmaster -B
   >2048 -i -o -F -D/var/lib/pgsql
   
   >Thanks
   >Lars
   
   Upgrade to v7.0.3 *at the very least* ... v7.1 is in final stages of its 
   release cycle, and should be out over the next week or so ...
   
   But, each version that we've released has had memory leaks plugged, 
   performance increased and stability improved ... I wouldn't recommend
   to *anyone* to run anything older then 1 (maybe 2) releases older then
   what is the current release, for the above reasons ...
   
   
   --
   Marc G. Fournier                                 marc.fournier@acadiau.ca
   Senior Systems Administrator                            Acadia University
   
     "These are my opinions, which are not necessarily shared by my employer"
   
   

3. Re: stability problems

   Mitch Vincent <mitch@venux.net> — 2001-03-30T15:10:20Z

   Upgrade to 7.1 as soon as it's out (shouldn't be long now)..
   
   I successfully migrated a 6.4 database to a 7.1 database while 7.1 was in
   the early beta stages, a few minor problems but the entire process only took
   half an hour to complete..
   
   Good luck!
   
   -Mitch
   Software development :
   You can have it cheap, fast or working. Choose two.
   
   ----- Original Message -----
   From: "Lars Maschke" <lars@gmeiner.de>
   To: <    >
   Sent: Wednesday, March 28, 2001 5:42 AM
   Subject: stability problems
   
   
   > Hello Newsgroup
   >
   > I have stability problems with my Postgres 6.4 database. I am using
   PHP4.0.4
   > and get access to the db. Sometimes when about 10-20 clients are using the
   > website the postgres deamon shuts down and the message "no backend cache"
   > appears. The processor ist at 60%-80% and about 10-15 postgres processes
   are
   > on my linux machine. So what can i do ?
   >
   > My postgres-command is: /usr/lib/pgsql/bin/postmaster -B
   > 2048 -i -o -F -D/var/lib/pgsql
   >
   > Thanks
   > Lars
   >
   >
   >
   > ---------------------------(end of broadcast)---------------------------
   > TIP 6: Have you searched our list archives?
   >
   > http://www.postgresql.org/search.mpl
   >
   
   
   

4. Re: stability problems

   Brent R. Matzelle <bmatzelle@yahoo.com> — 2001-03-30T20:32:50Z

   --- Lars Maschke <lars@gmeiner.de> wrote:
   > Hello Newsgroup
   > 
   > I have stability problems with my Postgres 6.4 database. I am
   > using PHP4.0.4
   > and get access to the db. Sometimes when about 10-20 clients
   > are using the
   > website the postgres deamon shuts down and the message "no
   > backend cache"
   > appears. The processor ist at 60%-80% and about 10-15 postgres
   > processes are
   > on my linux machine. So what can i do ?
   > 
   > My postgres-command is: /usr/lib/pgsql/bin/postmaster -B
   > 2048 -i -o -F -D/var/lib/pgsql
   
   Postgres has had multiple enhancements and bug fixes since
   version 6.4.  I have had over 50 clients running simultaneously
   with no problems with Postgres 7.0.3 & PHP 4.0.4pl1 on Linux. 
   Please download and install a newer version.  If you need any
   help doing this then email the list.  Don't forget to the dump
   the database(s) first.  
   
   Brent
   
   __________________________________________________
   Do You Yahoo!?
   Get email at your own domain with Yahoo! Mail. 
   http://personal.mail.yahoo.com/?.refer=text
   
   

5. - dumping a tables' 'subtree'

   Marek PUBLICEWICZ <m.publicewicz@elka.pw.edu.pl> — 2001-04-02T07:50:38Z

   Hello,
   
       I'd like to ask, if anyone has written a tool, allowing to
   dump the tables (both the schema and the data), basing on the
   'base' table_name, specified by the user. The tables that the database
   consists of, form a tree (as a result of the relations), so what I'm
   looking for is a program (script), issuing the 'DROP *', 'CREATE *', 'COPY
   FROM ' commands in the proper order. pg-dump dumps the whole 'tree' - I'd
   like to be able to specify myself the 'root' of this 'tree'.
   
   I realize, that my influency in English makes the description more vague,
   than it should be :) sorry.
   
   				regards,  mark
   
   PS. The reason why I feel I'm in need of suach a thing is that in general,
   when I try do pg_dump the database I'm working with, I get the errors -
   sometimes the inherited constraints seem to be unappropriate (both in
   terms of definitions and with their names), the COPY FROM clause sometimes
   also (starting with a particular row) generates error. Analyzing this
   would be much more simple, if I focus on the 'subset' of the whole dump -
   200+ tables for me is just too big bunch of info.
   
   The other reason is, that all the tables form (logically) several parts -
   I keep them together, because the parts interact (joins occur) between one
   another. And I'd like to be able to dump a specific logical part.