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

Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
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:12:43
Message-ID: 1684.1160950363@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
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?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-10-15 22:15:27
Subject: Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns
Previous:From: David FetterDate: 2006-10-15 21:52:05
Subject: Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-10-15 22:15:27
Subject: Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns
Previous:From: David FetterDate: 2006-10-15 21:52:05
Subject: Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8

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