On 10/01/12 1:20 AM, Mr Dash Four wrote:
FWIW, it's probably the "'user: ' || u_name" expressions that result
in this specific failure.
I found what is the cause of this - I had to add an explicit cast on
all text expressions, like "user: "::text as well as u_name::text.
That way the problem goes away, so it should.
that doesn't make any sense at all.
'user: ' *is* text by default. I didn't notice you displaying your
table definitions, but assuming u_name is TExT or VARCHAR(...) it
should have worked without any explicit casts
if you broke the permissions on the pg_catalog so badly that the SQL
planner can't look up the data types of the fields of your own tables,
well, thats just wrong.
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
