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

Michael Long <mlong@datalong.com> 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



view thread (3+ messages)  latest in thread

Message-ID: <14937.1097262020@sss.pgh.pa.us>
Permalink:  ../14937.1097262020@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14937.1097262020@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, mlong@datalong.com
  Subject: Re: Altering column type causes unstable server and data loss.
  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>

* 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