Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 9A6A66321D6;
	Tue,  6 Jan 2009 05:24:56 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 10118-08; Tue,  6 Jan 2009 05:24:47 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from rv-out-0506.google.com (rv-out-0506.google.com
 [209.85.198.230])
	by mail.postgresql.org (Postfix) with ESMTP id 7718B62E68C;
	Tue,  6 Jan 2009 05:24:46 -0400 (AST)
Received: by rv-out-0506.google.com with SMTP id b25so9063933rvf.43
	for <multiple recipients>; Tue, 06 Jan 2009 01:24:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=wlsyNJ0wbh5Gi+gWOc26LCEHeYXE9m7IzXa1ipKm83U=;
	b=ToBn8FSbuC0dq/I6SLoS0nkrSmw54ezXTo3sr/lOfnTMrRJsLZKt0XkjE+1kJodjCY
	tAdMcWM/6eyKuL2B018aTW6joEo7nSM/G1Sk5cyAP983BLg+MuaBtToEwDHzfS/Bnoec
	pxMnlhSbfda9tDgOlKoY5unoQEQgCadtmVY3k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:references;
	b=oVGdC2nvwSNB1WkV/2WYQnwjHwQr0dHqr4mIuxSjsy5SkpBzF814TT0+L+iNGPfsjj
	ZUPl2XKu7up5GYAwMSElCgedKN/Qb5zkO7KWCp9sbq/O/rzcZpKC4aPklhZhyrWNiOt/
	JqFSJIUtuiZ4L/rkQRoSbS6P7lck0M5fOiwhM=
Received: by 10.141.29.20 with SMTP id g20mr10862329rvj.156.1231233883001;
	Tue, 06 Jan 2009 01:24:43 -0800 (PST)
Received: by 10.141.98.4 with HTTP; Tue, 6 Jan 2009 01:24:42 -0800 (PST)
Message-ID: <65937bea0901060124m1a6f389en21d38cc857f72b12@mail.gmail.com>
Date: Tue, 6 Jan 2009 14:54:42 +0530
From: "Gurjeet Singh" <singh.gurjeet@gmail.com>
To: "Scott Marlowe" <scott.marlowe@gmail.com>
Subject: Re: [HACKERS] ERROR: failed to find conversion function from
	"unknown" to text
Cc: "Pavel Stehule" <pavel.stehule@gmail.com>,
	"PGSQL General" <pgsql-general@postgresql.org>,
	"PGSQL Hackers" <pgsql-hackers@postgresql.org>
In-Reply-To: <dcc563d10901060113y4dd7ac43v7756bdbe0e81e16e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_50804_6326977.1231233882998"
References: <65937bea0901052223w162a977dyeaaf888a854f7324@mail.gmail.com>
	<162867790901052230l25b10f08qa35f56856b9cc4c6@mail.gmail.com>
	<65937bea0901052237j50657573i8c980f9f5f4814d5@mail.gmail.com>
	<162867790901052245l4e4fa9b2ydc03781b45b13276@mail.gmail.com>
	<65937bea0901060104n399cdec8ye5e2b8e247e5139a@mail.gmail.com>
	<dcc563d10901060113y4dd7ac43v7756bdbe0e81e16e@mail.gmail.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.001 tagged_above=0 required=5
	tests=HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 200901/73
X-Sequence-Number: 142158

------=_Part_50804_6326977.1231233882998
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe <scott.marlowe@gmail.com>wrote:

> On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh <singh.gurjeet@gmail.com>
> wrote:
> > I took your cue, and have formulated this solution for 8.3.1 :
>
> Is there a good reason you're running against a db version with known
> bugs instead of 8.3.5?  Seriously, it's an easy upgrade and running a
> version missing over a year of updates is not a best practice.
>

That's just a development instance that I have kept for long; actual issue
was on EDB 8.3.0.12, which the customer is using. As noted in the PS of
previous mail, the solution that worked for PG 8.3.1 didn't work on EDB
8.3.0.12, so had to come up with a different code for that!

Best regards,
-- 
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

Mail sent from my BlackLaptop device

------=_Part_50804_6326977.1231233882998
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe <span dir="ltr">&lt;<a href="mailto:scott.marlowe@gmail.com">scott.marlowe@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh &lt;<a href="mailto:singh.gurjeet@gmail.com">singh.gurjeet@gmail.com</a>&gt; wrote:<br>
&gt; I took your cue, and have formulated this solution for 8.3.1 :<br>
<br>
</div>Is there a good reason you&#39;re running against a db version with known<br>
bugs instead of 8.3.5? &nbsp;Seriously, it&#39;s an easy upgrade and running a<br>
version missing over a year of updates is not a best practice.<br>
</blockquote></div><br>That&#39;s just a development instance that I have kept for long; actual issue was on EDB 8.3.0.12, which the customer is using. As noted in the PS of previous mail, the solution that worked for PG 8.3.1 didn&#39;t work on EDB 8.3.0.12, so had to come up with a different code for that!<br>
<br>Best regards, <br>-- <br>gurjeet[.singh]@EnterpriseDB.com<br>singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com<br><br>EnterpriseDB &nbsp; &nbsp; &nbsp;<a href="http://www.enterprisedb.com">http://www.enterprisedb.com</a><br>
<br>Mail sent from my BlackLaptop device<br>

------=_Part_50804_6326977.1231233882998--