Re: PG 9.0 and standard_conforming_strings

From: Mark Mielke <mark(at)mark(dot)mielke(dot)cc>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG 9.0 and standard_conforming_strings
Date: 2010-02-03 19:30:15
Message-ID: 4B69CEC7.1080807@mark.mielke.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 02/03/2010 02:15 PM, Robert Haas wrote:
> The longer we wait before making an
> incompatible change, the more people will have adjusted their code to
> the new reality (or upgraded their drivers, etc.) and the fewer things
> will break.
>

In my experience, the opposite is true, although in this case, the
damage may already be done.

That is, the longer bad habits are allowed to form, the harder they are
to break, and the more code is written that may be broken. People won't
"upgrade" unless forced. At some point, the switch does have to be tripped.

Is now the time? I have no comment. I just don't want to see "never" be
the time, and if "never" is not the time, than "now" does not seem
impratical. That said, if you say we'll tell people to prepare for a
change in 9.0, and enforce the change in a later release, that is fine too.

Cheers,
mark

--
Mark Mielke<mark(at)mielke(dot)cc>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-02-03 19:32:47 Re: Making pg_config and pg_controldata output available via SQL
Previous Message Tom Lane 2010-02-03 19:29:14 Re: Add on_trusted_init and on_untrusted_init to plperl UPDATED [PATCH]