Re: pg_upgrade 8.3 to 9.0, shutdown is to slow

Am Donnerstag, den 27.01.2011, 12:09 -0500 schrieb Bruce Momjian:
> Scott Marlowe wrote:
> > > My initial reaction is that something is wrong with your system, either
> > > the I/O or the way it is being shutdown by the script. ?I would start to
> > > look in the script and do some pg_ctl tests starting/stopping the
> > > server.
> >
> > It could be that his application or whatever is making connections
> > while he's trying to do this. An open connection that's actually
> > doing something will stop a normal shutdown.
> >
> > Is there a reason the pg upgrade script does not use -m fast?
>
> Uh, well, I assume that the person has already shut down all db
> connections, and opened it only for super-users. If the system is not
> shutting down, that should signal to the user that they have not locked
> down the system properly. We would not want someone to connect during
> pg_upgrade processing, and doing -m fast is not going to help with that.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
>

Hi,

well, i shut down every client connection that could occur, but with a
ps auxf i get following output:

postgres 26255 0.0 0.0 426396 2044 ? Ss 14:21 0:00 \_ postgres: writer
process
postgres 26257 0.0 0.0 154368 1616 ? Ss 14:21 0:00 \_ postgres: stats
collector process
postgres 26258 0.0 0.1 427612 4188 ? Ss 14:21 0:00 \_ postgres: grepo
DB_NAME LOCAL_IP(PORT) idle

so there are some connections, but as far as i can say, nothing from a
client program, these connections belong to postgres itself??!? is that
possible? pg_upgrade has to check the tables anyway, so there must be
this connection, or am i wrong?!?

greetz