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

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 23:32:22
Message-ID: 20061015233222.GD7037@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Sun, Oct 15, 2006 at 07:07:18PM -0400, Tom Lane wrote:
> David Fetter <david(at)fetter(dot)org> writes:
> > 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.
>
> No, we won't; we are not in the business of fixing Perl bugs.

My point exactly.

> You haven't given any reason why someone who is using 5.6 and is
> happy with it shouldn't be able to continue to use it with PG.

In my experience, people aren't "happy with" 5.6. Instead, they've
got a mandate to maintain support for it, and this could be an
argument for upgrading.

Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter

Remember to vote!

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Delight Chen 2006-10-16 01:42:06 BUG #2693: Abut SQL ASCII through JDBC
Previous 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

Browse pgsql-hackers by date

  From Date Subject
Next Message mark 2006-10-15 23:55:42 Re: Postgresql Caching
Previous Message mark 2006-10-15 23:26:49 Re: Postgresql Caching