Re: Slightly inconsistent behaviour in regproc?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Slightly inconsistent behaviour in regproc?
Date: 2003-10-28 06:25:44
Message-ID: 3F9E0BE8.20603@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>Only regproc adds the unnecessary pg_catalog. qualification, why is that?
>
>
> Er, I couldn't see the part of your example where that happened?

Basically, my question is why ::regproc alone always addes the catalogue
qualification in this case?

Rows below correspond to:

::regtype
::regtype
::regprocedure
::regproc

-[ RECORD 1 ]----------------------------------------
castsource | "char"
casttarget | text
castfunc | text("char")
castfunc2 | pg_catalog.text

eg. Why is it not:

-[ RECORD 1 ]----------------------------------------
castsource | "char"
casttarget | text
castfunc | text("char")
castfunc2 | text

Or even:

-[ RECORD 1 ]----------------------------------------
castsource | pg_catalog."char"
casttarget | pg_catalog.text
castfunc | pg_catalog.text("char")
castfunc2 | pg_catalog.text

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-10-28 06:44:08 limiting parallelism in "make check"
Previous Message Bruce Momjian 2003-10-28 06:10:55 Re: Horology failures