From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
---|---|
To: | "Rodrigo Rosenfeld Rosas" <rr(dot)rosas(at)gmail(dot)com>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: wrong search_path being used |
Date: | 2013-01-09 22:09:03 |
Message-ID: | 20130109220903.255790@gmx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Rodrigo Rosenfeld Rosas wrote:
> Tom Lane wrote:
>> There have been discussions about changing that
> if I understand it correctly, you do consider it a bug but you
> don't want to backport a fix because it might break existent
> behavior in some dbs, right?
No, there has been discussion about whether different behavior
would be better in future major releases, but no consensus has been
reached.
>> but we wouldn't treat it as a back-patchable bug fix, because
>> it would almost certainly break things for somebody.
>
> But it is not clear to me if you're willing to fix it for 9.2.3
> for instance?
Back-patching means changing things in a minor release, where
things only change after the second dot. We don't make changes in
user-visible behavior like this in minor releases; so no, we would
not make a change like this in 9.2.3 or any other 9.2 version.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Rodrigo Rosenfeld Rosas | 2013-01-10 01:09:18 | Re: wrong search_path being used |
Previous Message | Kevin Grittner | 2013-01-09 20:27:08 | Re: BUG #7795: Cannot choose UTF-8 encoding for initdb |