Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 979211337B93 for ; Sat, 9 Apr 2011 11:23:00 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 13933-06 for ; Sat, 9 Apr 2011 14:22:41 +0000 (UTC) Received: from news.hub.org (news.hub.org [200.46.204.72]) by mail.postgresql.org (Postfix) with ESMTP id 579AE1337B61 for ; Sat, 9 Apr 2011 11:22:41 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.4/8.14.4) with ESMTP id p39EMeMe015455 for ; Sat, 9 Apr 2011 11:22:40 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.4/8.14.4/Submit) id p39EL2wM012437 for pgsql-admin@postgresql.org; Sat, 9 Apr 2011 11:21:02 -0300 (ADT) (envelope-from news) From: Erwin Brandstetter X-Newsgroups: pgsql.admin Subject: 20110408pg upgrade fix: How do I know if I am being affected before errors occur Date: Sat, 9 Apr 2011 07:21:03 -0700 (PDT) Organization: http://groups.google.com Lines: 17 Message-ID: <9cd57df6-665f-41b0-899e-efe070e2e50e@f30g2000yqa.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Complaints-To: groups-abuse@google.com Complaints-To: groups-abuse@google.com Injection-Info: f30g2000yqa.googlegroups.com; posting-host=80.109.13.165; posting-account=Ir5o5AoAAABY9pVbvZJ-5F12wPWZbHFI User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0,gzip(gfe) To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=-10 required=5 tests=BAYES_40=-0.001, FREEMAIL_FROM=0.001, T_RP_MATCHES_RCVD=-0.01, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201104/71 X-Sequence-Number: 37252 Hello! In connection with the recently discovered bug with pg_upgrade: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix If I an not sure whether pg_upgrade or pg_migrate has been applied on certain databases in the past: - How do I know if I am being affected by the bug _before_ errors occur? - Can applying the proposed fix break anything if the db wasn't affected to begin with? Information as to that is missing in the mail to pgsql- announce@postgresql.org as well as on the wiki-page. Thank You! Regards Erwin