dbTalk Databases Forums  

[BUGS] 8.0.0beta1 small inconsistency in pg_aggregate listing

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss [BUGS] 8.0.0beta1 small inconsistency in pg_aggregate listing in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Fabien COELHO
 
Posts: n/a

Default [BUGS] 8.0.0beta1 small inconsistency in pg_aggregate listing - 08-20-2004 , 08:20 AM







I've noticed a minor inconsistency when listing pg_aggregate in
current 8.0.0beta1 version.

psql> SELECT aggfnoid FROM pg_aggregate;

4 functions are not schema qualified:
count
bool_and
bool_or
every

although all others are shown with a schema name:
pg_catalog.avg
pg_catalog.sum
pg_catalog.max
pg_catalog.min
...

However psql \da show all of them in pg_catalog, as expected.

I cannot see the difference in the initialization script to explain that.
Maybe something wrong with the regproc type?

--
Fabien Coelho - coelho (AT) cri (DOT) ensmp.fr

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply With Quote
  #2  
Old   
Tom Lane
 
Posts: n/a

Default Re: [BUGS] 8.0.0beta1 small inconsistency in pg_aggregate listing - 08-20-2004 , 10:45 AM






Fabien COELHO <coelho (AT) cri (DOT) ensmp.fr> writes:
Quote:
Maybe something wrong with the regproc type?
regprocout doesn't schema-qualify if the function name is unique without
it.

Of course, the function name isn't necessarily unique *with* it, either,
but regproc can't do anything about that. Cast to regprocedure if you
want to see a more helpful display of the function.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match


Reply With Quote
  #3  
Old   
Fabien COELHO
 
Posts: n/a

Default Re: [BUGS] 8.0.0beta1 small inconsistency in pg_aggregate listing - 08-20-2004 , 10:58 AM




Quote:
Maybe something wrong with the regproc type?

regprocout doesn't schema-qualify if the function name is unique without
it.
Ok. Maybe too clever, as I couldn't guess by looking at it.

Quote:
Of course, the function name isn't necessarily unique *with* it, either,
but regproc can't do anything about that. Cast to regprocedure if you
want to see a more helpful display of the function.
Much better indeed.

Thanks a lot for the light. Have a nice day.

--
Fabien Coelho - coelho (AT) cri (DOT) ensmp.fr

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.