On Tue, 2002-02-12 at 16:16, Tom Lane wrote:
> And this would be worse.
>
> If you don't care about your data, you can "initdb" to get rid of the
> messed-up database. If you do care, you shouldn't be doing any of the
> above.
The problem here, is a lot of programmers "start-stopping" the database
continuosly... :( And I can't make anything, because they need total
control over the database.
Here it is a bit of log after start the database in her actually state:
FATAL 1: The database system is starting up
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: BackendStartup: forked pid=18416 socket=8
DEBUG: reaping dead processes
DEBUG: child process (pid 18416) exited with exit
code 0
DEBUG: INSERT @ 0/48F85360: prev 0/48F85320; xprev
0/0; xid 0: XLOG - checkpoint: redo 0/48F85360; undo 0/0; sui 19; xid
2482396;
oid 3736683; shutdown
DEBUG: XLogFlush: request 0/48F853A0; write 0/48F8
5360; flush 0/48F85360
DEBUG: database system is ready
DEBUG: proc_exit(0)
DEBUG: shmem_exit(0)
DEBUG: exit(0)
DEBUG: reaping dead processes
DEBUG: BackendStartup: forked pid=18422 socket=8
DEBUG: connection: host=192.168.141.208 user=xxx
database=example
And make this, to 20 backend processes!!.
Tom say me to run "initdb", but... If possible to clean this wal's???
Thank you very much from here to Tom and the rest of pg-admin people.
Regards, Manuel.
--
Manuel Trujillo manueltrujillo@dorna.es
Technical Engineer http://www.motograndprix.com
Dorna Sports S.L. +34 93 4702864