Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Rename the members of CommandDest enum so

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Rename the members of CommandDest enum so
Date: 2005-11-03 17:55:37
Message-ID: 25785.1131040537@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Marc G. Fournier wrote:
>> Is this an appropriate commit for post-Beta?  Does it fix a critical bug 
>> that will prevent a release from happening? :(

> Well, I asked -hackers before committing, and there were no objections,
> plus there were a couple of messages that weren't actual encouragements
> but I took as sign of approval.

Yeah, I would have told him "no" if I thought there were any risk of
breaking things, but renaming some constants seems a pretty safe
activity --- the compiler will catch any overlooked cases.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-11-03 18:02:13
Subject: Re: Reducing the overhead of NUMERIC data
Previous:From: Tom LaneDate: 2005-11-03 17:53:01
Subject: Re: Exclusive lock for database rename

pgsql-committers by date

Next:From: Alvaro HerreraDate: 2005-11-03 18:03:23
Subject: press - pr: Fix broken markup, a couple of typos and set the release
Previous:From: Tom LaneDate: 2005-11-03 17:45:30
Subject: pgsql: Thinking further, it seems we had better also copy down

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group