pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Jon Nelson <jnelson+pgsql@jamponi.net>
Cc: " <pgsql-bugs@postgresql.org>
Cc: " <pgsql-bugs@postgresql.org>
Subject: Re: [PERFORM] typoed column name, but postgres didn't grump
Date: Fri, 29 Oct 2010 20:24:54 -0400
Message-ID: <4CC661F3-5686-4A46-BF58-547601CB59B3@gmail.com> (raw)
In-Reply-To: <9887.1288389232@sss.pgh.pa.us>
References: <AANLkTimYMA8D2h4-jHK5vD032jWwig1iJmW6uF-3i=Bx@mail.gmail.com>
	<4480.1288374498@sss.pgh.pa.us>
	<4CCACE6E0200002500036F95@gw.wicourts.gov>
	<6240.1288379246@sss.pgh.pa.us>
	<AANLkTim35FrP1EyZRmnotKSw=2rq8JNVutkitn9PXwFp@mail.gmail.com>
	<4CCADE440200002500036FB2@gw.wicourts.gov>
	<4CCADE440200002500036FB2@gw.wicourts.gov>
	<8216.1288383162@sss.pgh.pa.us>
	<4CCAE6650200002500036FC3@gw.wicourts.gov>
	<0E628919-9700-47B7-9436-41CEB09DC94F@gmail.com>
	<9887.1288389232@sss.pgh.pa.us>

On Oct 29, 2010, at 5:53 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Yeah, I think we're going to have to live with it, at least for 8.4.  One could make an argument that 9.0 is new enough we could get away with a small behavior change to avoid a large amount of user confusion.  But that may be a self-serving argument based on wanting to tamp down the bug reports rather than a wisely considered policy decision...  so I'm not sure I quite buy it.
> 
> Well, tamping down the bug reports is good from the users' point of view
> too.
> 
> The argument for not changing it in the back branches is that there
> might be someone depending on the 8.4/9.0 behavior.  However, that seems
> moderately unlikely.  Also, if we wait, that just increases the chances
> that someone will come to depend on it, and then have a problem when
> they migrate to 9.1.  I think the "risk of breakage" argument has a lot
> more force when considering long-standing behaviors than things we just
> recently introduced.

I'm not entirely sure that a behavior we released well over a year ago can be considered "just recently introduced"...

...Robert


view thread (23+ messages)  latest in thread

Message-ID: <4CC661F3-5686-4A46-BF58-547601CB59B3@gmail.com>
Permalink:  ../4CC661F3-5686-4A46-BF58-547601CB59B3@gmail.com/
Also on:    postgresql.org/message-id/4CC661F3-5686-4A46-BF58-547601CB59B3@gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: robertmhaas@gmail.com, tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, jnelson+pgsql@jamponi.net, pgsql-bugs@postgresql.org
  Subject: Re: [PERFORM] typoed column name, but postgres didn't grump
  In-Reply-To: <4CC661F3-5686-4A46-BF58-547601CB59B3@gmail.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