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

Re: BUG #2683: spi_exec_query in plperl returns column

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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
Date: 2006-10-16 04:10:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-hackers
David Fetter wrote:
> 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.

Or an argument to dump PostgreSQL.

  Bruce Momjian   bruce(at)momjian(dot)us

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

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-10-16 04:15:59
Subject: Re: Threaded python on FreeBSD
Previous:From: Jeremy DrakeDate: 2006-10-16 03:36:25
Subject: Re: constraints in query plans

pgsql-bugs by date

Next:From: David FetterDate: 2006-10-16 04:41:58
Subject: Re: BUG #2683: spi_exec_query in plperl returns column names which are not marked as UTF8
Previous:From: Delight ChenDate: 2006-10-16 01:42:06
Subject: BUG #2693: Abut SQL ASCII through JDBC

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