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: Bruce Momjian <bruce(at)momjian(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 names which are not marked as UTF8
Date: 2006-10-16 14:00:13
Message-ID: 19964.1161007213@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
David Fetter <david(at)fetter(dot)org> writes:
> 1.  We can continue to support 5.6 until we can't any more, and
> statistically speaking that "can't any more" is quite likely to happen
> between two minor releases.

That's a silly and unfounded assertion.  What sort of event do you
foresee that is going to make us conclude that we have to remove 5.6
support in a minor release?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2006-10-16 14:00:34
Subject: Re: Postgresql Caching
Previous:From: Marko KreenDate: 2006-10-16 13:35:33
Subject: Re: Getting the type Oid in a CREATE TYPE output function

pgsql-bugs by date

Next:From: Martijn van OosterhoutDate: 2006-10-16 14:10:44
Subject: Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns
Previous:From: JakubDate: 2006-10-16 08:18:11
Subject: BUG #2695: Randomly repeated query execution

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