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 2A94232A089 for ; Sat, 9 Oct 2004 04:02:11 +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 42229-01 for ; Sat, 9 Oct 2004 03:02:00 +0000 (GMT) Received: from server18.pronicsolutions.com (server18.pronicsolutions.com [66.103.131.81]) by svr1.postgresql.org (Postfix) with ESMTP id 06A1832B409 for ; Sat, 9 Oct 2004 04:01:59 +0100 (BST) Received: from pool-129-44-186-84.bos.east.verizon.net ([129.44.186.84] helo=[192.168.1.3]) by server18.pronicsolutions.com with esmtpa (Exim 4.43) id 1CG7Ua-00059N-Iy for pgsql-admin@postgresql.org; Fri, 08 Oct 2004 23:01:56 -0400 Message-ID: <41675516.6060103@datalong.com> Date: Fri, 08 Oct 2004 23:03:50 -0400 From: Micahael Long User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040928 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-admin@postgresql.org Subject: Re: Altering column type causes unstable server and data 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> <14937.1097262020@sss.pgh.pa.us> In-Reply-To: <14937.1097262020@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server18.pronicsolutions.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - datalong.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/138 X-Sequence-Number: 15131 >pgsql-bugs is much more appropriate, especially for problem reports >against a beta version. > > > I will keep this in mind in the outside chance that I run into another issue :) >I tried to reproduce this without any success. Given the inconsistency >of the behavior, I'm wondering about hardware flakiness on your machine. > > > As I get some time I will try to create a scenario to reproduce the problem. While thinking about the sequence of events that led to this problem I realized that it will take some controlled testing to isolate what went wrong. I may be that the alter column type command had nothing to do with it. >>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? > > # TYPE DATABASE USER CIDR-ADDRESS METHOD local all all trust # IPv4-style local connections: # host all all 127.0.0.1/32 trust host all all 192.168.1.0/24 trust # IPv6-style local connections: # host all all ::1/128 trust