| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: strange permission error |
| Date: | 2012-10-01 08:47:09 |
| Message-ID: | 5069588D.3050502@hogranch.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phoenix Kiula | 2012-10-01 10:26:04 | Again, problem with pgbouncer |
| Previous Message | Carrington, Matthew (Produban) | 2012-10-01 08:43:21 | Re: pg_upgrade: out of memory |