From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
Cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: FUNCTIONs and CASTs
Date: Fri, 15 Feb 2008 17:32:25 -0500
Message-ID: <655.1203114745@sss.pgh.pa.us> (raw)
In-Reply-To: <47B5D790.4090509@ultimeth.com>
References: <47B4C9E4.8090002@ultimeth.com>
<20670.1203031191@sss.pgh.pa.us>
<47B4EF3E.4090608@ultimeth.com>
<47B55DA1.1060706@archonet.com>
<47B5D790.4090509@ultimeth.com>
"Dean Gibson (DB Administrator)" <postgresql@ultimeth.com> writes:
> Again, you are not understanding my point. My point was that specifying
> tablename.columnname%TYPE notation doesn't help with the performance
> problem; I have to explicitly cast the parameter in the body of the
> function.
The reason for the lack of communication is that no one else believes
that premise. Casting a value to the same type it already has is
demonstrably a no-op.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, postgresql@ultimeth.com
Subject: Re: FUNCTIONs and CASTs
In-Reply-To: <655.1203114745@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox