Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 385E61337B79 for ; Thu, 27 Jan 2011 13:46:13 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 37490-02 for ; Thu, 27 Jan 2011 17:46:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from extern.innogames.de (extern.innogames.de [80.252.99.240]) by mail.postgresql.org (Postfix) with ESMTP id 0D6831337B4E for ; Thu, 27 Jan 2011 13:46:05 -0400 (AST) Received: from [172.16.5.29] (unknown [212.48.107.10]) by extern.innogames.de (Postfix) with ESMTPA id EE88228F047; Thu, 27 Jan 2011 18:46:03 +0100 (CET) Subject: Re: pg_upgrade 8.3 to 9.0, shutdown is to slow From: Bernhard Schrader To: Bruce Momjian Cc: Scott Marlowe , Kevin Grittner , pgsql-admin@postgresql.org In-Reply-To: <201101271709.p0RH9f421528@momjian.us> References: <201101271709.p0RH9f421528@momjian.us> Content-Type: text/plain; charset="UTF-8" Organization: Innogames GmbH Date: Thu, 27 Jan 2011 18:46:04 +0100 Message-ID: <1296150364.2330.15.camel@schrader-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201101/174 X-Sequence-Number: 36614 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 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