Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 02DB4632206; Tue, 6 Jan 2009 05:29:12 -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 11366-09; Tue, 6 Jan 2009 05:29:03 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mail.postgresql.org (Postfix) with ESMTP id 964F46321FA; Tue, 6 Jan 2009 05:29:02 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id j4so4312285wah.19 for ; Tue, 06 Jan 2009 01:29:00 -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 :content-transfer-encoding:content-disposition:references; bh=1XVdB3lxdkb/ZFf/tJU4G4uTHiTmzBeYqbbX2+kXkZc=; b=bDimhHRGFIE1LGSJlQsmtPC3Z8hMx7j7ZjurUddKEjbeBiBK/0+bM416zBfeKo0JhM NLfNf7LDZgUopAlIDR2dMNzYz/uhFpq0obN+CDyGPleeXMrS/FPc1BYJ8aZYkZWK3Fci HlDnAR7QiBIbFMdpoKMXFJPTiUlU0ZwjwTV9w= 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:content-transfer-encoding:content-disposition :references; b=WG/DsBgqA+/KazmWUSIkl1MQ9ELQbNv7ofHG7PoHbiwfk93NFOIKLTUMNkS9EK5BDA y5Gri0CHgeC6CcrOVH/Cr+p509N8allYhD7Fm3ModMVPw0vY0Lo2aja8jYFGEW5Fqd+i KnIRHykRS/MAwcXPleZG/RyZvG6/eVP8yG1nw= Received: by 10.114.24.1 with SMTP id 1mr14381942wax.179.1231234140112; Tue, 06 Jan 2009 01:29:00 -0800 (PST) Received: by 10.115.108.3 with HTTP; Tue, 6 Jan 2009 01:29:00 -0800 (PST) Message-ID: Date: Tue, 6 Jan 2009 02:29:00 -0700 From: "Scott Marlowe" To: "Gurjeet Singh" Subject: Re: [HACKERS] ERROR: failed to find conversion function from "unknown" to text Cc: "Pavel Stehule" , "PGSQL General" , "PGSQL Hackers" In-Reply-To: <65937bea0901060124m1a6f389en21d38cc857f72b12@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <65937bea0901052223w162a977dyeaaf888a854f7324@mail.gmail.com> <162867790901052230l25b10f08qa35f56856b9cc4c6@mail.gmail.com> <65937bea0901052237j50657573i8c980f9f5f4814d5@mail.gmail.com> <162867790901052245l4e4fa9b2ydc03781b45b13276@mail.gmail.com> <65937bea0901060104n399cdec8ye5e2b8e247e5139a@mail.gmail.com> <65937bea0901060124m1a6f389en21d38cc857f72b12@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200901/75 X-Sequence-Number: 142160 On Tue, Jan 6, 2009 at 2:24 AM, Gurjeet Singh wrote: > On Tue, Jan 6, 2009 at 2:43 PM, Scott Marlowe > wrote: >> >> On Tue, Jan 6, 2009 at 2:04 AM, Gurjeet Singh >> 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! Ahh, ok. I was just worried you were ignoring updates. I don't know anything about the numbering scheme for EDB. What does 8.3.0.12 translate to in regular pgsql versions?