pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Micahael Long <mlong@datalong.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Altering column type causes unstable server and data
Date: Fri, 08 Oct 2004 23:03:50 -0400
Message-ID: <41675516.6060103@datalong.com> (raw)
In-Reply-To: <14937.1097262020@sss.pgh.pa.us>
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>


>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





view thread (3+ messages)

Message-ID: <41675516.6060103@datalong.com>
Permalink:  ../41675516.6060103@datalong.com/
Also on:    postgresql.org/message-id/41675516.6060103@datalong.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mlong@datalong.com
  Subject: Re: Altering column type causes unstable server and data
  In-Reply-To: <41675516.6060103@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> <14937.1097262020@sss.pgh.pa.us> <41675516.6060103@datalong.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox