X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 02B8CD8DD1 for ; Mon, 21 Nov 2005 11:03:49 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34848-01 for ; Mon, 21 Nov 2005 15:03:52 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 14640D8323 for ; Mon, 21 Nov 2005 11:03:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jALF3jVu001720; Mon, 21 Nov 2005 10:03:45 -0500 (EST) To: "=?iso-8859-1?Q?H=E9lder_M._Vieira?=" cc: pgsql-sql@postgresql.org Subject: Re: max() unexpected type conversion In-reply-to: <000901c5ee99$c275e380$580bfea9@hmv02> References: <000901c5ee99$c275e380$580bfea9@hmv02> Comments: In-reply-to "=?iso-8859-1?Q?H=E9lder_M._Vieira?=" message dated "Mon, 21 Nov 2005 12:47:40 +0000" Date: Mon, 21 Nov 2005 10:03:45 -0500 Message-ID: <1719.1132585425@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.004 required=5 tests=[AWL=0.004] X-Spam-Score: 0.004 X-Spam-Level: X-Archive-Number: 200511/179 X-Sequence-Number: 23430 "=?iso-8859-1?Q?H=E9lder_M._Vieira?=" writes: > If max() operates on a 'varchar' type column, the result appears with 'text' > type. > Should I expect this behaviour in the current and later versions ? This is true of just about everything, not only max() -- there are *no* functions yielding varchar in recent PG releases. regards, tom lane