From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |
Date: | 2006-10-15 22:50:00 |
Message-ID: | 20061015225000.GC7037@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Sun, Oct 15, 2006 at 06:12:43PM -0400, Tom Lane wrote:
> David Fetter <david(at)fetter(dot)org> writes:
> > On Sun, Oct 15, 2006 at 04:43:17PM -0400, Tom Lane wrote:
> >> ISTM the real question is what do we buy if we make such a
> >> restriction? Getting rid of a few small ifdefs doesn't seem like
> >> an adequate reason. Is there some major improvement we could
> >> make?
>
> > UTF-8 handling much improved in 5.8.
>
> And? Sure there are good reasons why someone might want to use 5.8
> instead of 5.6, but how is that a reason for us to remove 5.6
> support?
At some point, we will find something where we will have to duplicate
some large hunk of 5.8's functionality to support 5.6. Why wait for
that to happen? Murphy's Law says it will happen in a bug fix between
two minor releases.
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-15 23:07:18 | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |
Previous Message | David Fetter | 2006-10-15 22:16:31 | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-15 23:07:18 | Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8 |
Previous Message | Tom Lane | 2006-10-15 22:19:12 | Re: Threaded python on FreeBSD |