> For diferent shutdown modes use
>
> SMART_SHUTDOWN : kill -s TERM
> "Smart" mode waits for all the clients to disconnect
>
> FAST_SHUTDOWN : kill -s INT
> "Fast" mode does not wait for clients to disconnect
>
> IMMEDIATE_SHUTDOWN : kill -s QUIT
> "Immediate" mode will abort all server processes without clean shutdown.
> This will lead to a recovery run on restart.
>
> RELOAD : kill -s HUP
>
> Take a look here - this is a windows console for PostgreSQL
> http://gborg.postgresql.org/project/winmaster/projdisplay.php
>
>
> ----- Original Message -----
> From: "frank_lupo"
> To: "pgsql-cygwin"
> Sent: Friday, February 07, 2003 11:10 AM
> Subject: [CYGWIN] shutdown postgres problem
>
>
> > I work in Win NT 4.0 using the following version:
> > PostgreSQL 7.2.3 on i686-pc-cygwin, compiled by GCC 2.95.3-5
> >
> > Every n
ight, I
n
eed to shut down Postgres, using the command line
> > net stop postmaster
> >
> > Later, the database is starting again, using the command line
> > net start postmaster
> >
> > If some user is still connected to the database, the shut down process
> fails
> > and I find some processes "postgres.exe" still active in the server.
> > In order to solve the problem and make the database again starting, I kill
> all the "postgres.exe" processes
> > kill process #process number ("postgres.exe")
> > kill process #process number ("postgres.exe")
> > ................
> > rm $PGDATA/postmaster.pid
> >
> > then
> > net start postmaster
> >
> > Looking at the log file, I see the following messages
> > DEBUG: pq_recvbuf: recv() failed: Connection reset by peer
> > DEBUG: fast shutdown request
> > DEBUG: aborting any active t
> > ransacti
> > o
> > ns
> > FAT
AL 1: T
h
is connection has been terminated by the administrator.
> > FATAL 1: This connection has been terminated by the administrator.
> > DEBUG: ReceiveSharedInvalidMessages: cache state reset
> > FATAL 1: The database system is shutting down
> > DEBUG: database system was interrupted at 2003-02-06 19:52:23 WEST
> > DEBUG: checkpoint record is at 7/EBB80A30
> > DEBUG: redo record is at 7/EBB80A30; undo record is at 0/0; shutdown
> FALSE
> > DEBUG: next transaction id: 1621877; next oid: 43682810
> > DEBUG: database system was not properly shut down; automatic recovery in
> progress
> > DEBUG: redo starts at 7/EBB80A70
> > DEBUG: ReadRecord: record with zero length at 7/EBB98230
> > DEBUG: redo done at 7/EBB98208
> > DEBUG: database system is ready
> >
> >
> > Sometimes, the shut down process runs correctly even with some users
> connected.
> >
> > Do you have any idea on t
he way t
o
solve this problem ?
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.449 / Virus Database: 251 - Release Date: 27/01/2003
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
I still have the same problems. This is the result of the commando ps -ef
$ ps -ef
UID PID PPID TTY STIME COMMAND
SYSTEM 108 1 ? Jan 3 /usr/bin/cygrunsrv
SYSTEM 81 108 ? Jan 3 /usr/sbin/cron
postgres 175 1 ? Feb 8 /usr/bin/postgres
postgres 604 175 ? Feb 8 /usr/bin/postgres
postgres 148 604 ? Feb 8 /usr/bin/postgres
postgres 458 175 ? 07:53:36 /usr/bin/postgres
postgres 425 175 ? 18:14:34 <defunct>
Admini
st 6
1
5 1 con 23:10:53 /usr/bin/bash
Administ 612 615 con 23:12:49 /usr/bin/ps
Help me
Bye !!
Frank Lupo (Wolf) !!
/\_ _/\
\ o o /
--ooo-----ooo---
Bye !!
Frank Lupo (Wolf) !!
/\_ _/\
\ o o /
--ooo-----ooo---
Bye !!
Frank Lupo (Wolf) !!
/\_ _/\
\ o o /
--ooo-----ooo---
--
Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f
Sponsor:
Realizza un desiderio, con Conto Privilegiato basta un click fare di un sogno realtà.
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1248&d=14-2
