X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5851732A108 for ; Fri, 8 Oct 2004 20:00:56 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23372-09 for ; Fri, 8 Oct 2004 19:00:23 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 903CE32A0AF for ; Fri, 8 Oct 2004 20:00:23 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i98J0Kfu014938; Fri, 8 Oct 2004 15:00:20 -0400 (EDT) To: Michael Long Cc: pgsql-admin@postgresql.org Subject: Re: Altering column type causes unstable server and data loss. In-reply-to: <41662827.8030207@datalong.com> References: <415F87D7.5000800@datalong.com> <28880.1096780739@sss.pgh.pa.us> <415F8EC5.9040504@datalong.com> <415F9A9F.6090500@datalong.com> <29421.1096785225@sss.pgh.pa.us> <415FA1FB.9000306@datalong.com> <3071.1096822055@sss.pgh.pa.us> <41606106.2080006@datalong.com> <9756.1096842275@sss.pgh.pa.us> <41662827.8030207@datalong.com> Comments: In-reply-to Michael Long message dated "Fri, 08 Oct 2004 01:39:51 -0400" Date: Fri, 08 Oct 2004 15:00:20 -0400 Message-ID: <14937.1097262020@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.1 tagged_above=0.0 required=5.0 tests=NO_DNS_FOR_FROM X-Spam-Level: * X-Archive-Number: 200410/135 X-Sequence-Number: 15128 Michael Long writes: > If this is not the correct place report this type thing please let me > know and I will post it to the correct location. pgsql-bugs is much more appropriate, especially for problem reports against a beta version. > I was able to successfully alter a column of type date to > varchar(20). However now when I perform selects on the table I will > either get the results as expected, have the psql connection to the > server broken, or have the server itself hang. I tried to reproduce this without any success. Given the inconsistency of the behavior, I'm wondering about hardware flakiness on your machine. I could believe that ALTER TABLE has a bug causing it to produce a corrupt output table, but if the table is corrupt then "select *" should produce consistently wrong answers or a consistent crash. In any case, I made a table matching your table schema, put a few rows in it, did the ALTER, and was still able to SELECT * from it. So if there's a bug it requires additional triggering conditions you haven't mentioned. > The other interesting behavior is that prior to altering the table I > could connect to the server from my Win2k box. After this point I get > the message "FATAL: missing or erroneous pg_hba.conf file." This file > not only exists but has not be modified by me during this time frame. So what's in the file now? regards, tom lane