David Johnston wrote
> Or feel free to peruse the release notes for 9.2, this behavior change
> should be documented if intentional.
Reading said notes it appears that the "returns NULL" behavior compensates
for a concurrent DROP of an existing/known OID. Since your issue is that
the object was n
rummandba wrote
> HI,
>
> I am working on Postgresql 9.1.3.
> I executed the following query and got an error:
> select relname, pg_size_pretty(pg_table_size(relname::text)) as s from
> pg_stat_user_tables order by pg_table_size(relname::text) desc limit 10;
> ERROR: relation "tab_20130206" doe
AI Rumman writes:
> I executed the following query and got an error:
> select relname, pg_size_pretty(pg_table_size(relname::text)) as s from
> pg_stat_user_tables order by pg_table_size(relname::text) desc limit 10;
> ERROR: relation "tab_20130206" does not exist
Use the OID, not the relname,
HI,
I am working on Postgresql 9.1.3.
I executed the following query and got an error:
select relname, pg_size_pretty(pg_table_size(relname::text)) as s from
pg_stat_user_tables order by pg_table_size(relname::text) desc limit 10;
ERROR: relation "tab_20130206" does not exist
That table does n
