Re: regclass error reports improperly downcased - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: regclass error reports improperly downcased
Date
Msg-id 52812450.4070307@enova.com
Whole thread Raw
In response to Re: regclass error reports improperly downcased  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: regclass error reports improperly downcased  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11/8/13 2:21 PM, Tom Lane wrote:
> Jim Nasby <jnasby@enova.com> writes:
>> Ahh, duh. Hrm... I ran across this because someone here got confused by this:
>
>> SELECT pg_total_relation_size( schema_name || '.' || relname ) FROM pg_stat_all_tables
>> ERROR: relation "moo" does not exist
>
> Personally I'd do that like
>
>        select pg_total_relation_size(oid) from pg_class where ...
>
> and avoid fooling with regclass conversion at all.

Yeah, that's what I did in this case. I'm just trying to make it more obvious to users that make this mistake.

Is anyone opposed to some kind of hint?
-- 
Jim Nasby, Lead Data Architect   (512) 569-9461



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add %z support to elog/ereport?
Next
From: Andres Freund
Date:
Subject: Re: better atomics - spinlock fallback?