Re: BUG #2683: spi_exec_query in plperl returns column - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #2683: spi_exec_query in plperl returns column
Date
Msg-id 200610160410.k9G4AgG11466@momjian.us
Whole thread Raw
In response to Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8  (David Fetter <david@fetter.org>)
Responses Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8  (David Fetter <david@fetter.org>)
List pgsql-bugs
David Fetter wrote:
> On Sun, Oct 15, 2006 at 07:07:18PM -0400, Tom Lane wrote:
> > David Fetter <david@fetter.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.

Or an argument to dump PostgreSQL.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: David Fetter
Date:
Subject: Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8
Next
From: David Fetter
Date:
Subject: Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8