Re: is prefix pg_ reservated ?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: is prefix pg_ reservated ?
Date: 2012-08-07 12:41:03
Message-ID: CA+TgmoaZY=ymr9_KcDkQd_SD3-F9bo_HSq7_qPogJJYpLchSPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 7, 2012 at 7:16 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hello all
>
> I found strange behave of postgresql. I would to use name
> pg_stat_get_some for custom function. Probably it is not smart from
> me, because I found so functions that has prefix pg are not searched
> via search_path.
>
> postgres=# select public.pg_stat_get_creation_time('xxx'::regclass);
> pg_stat_get_creation_time
> -------------------------------
> 2012-08-07 12:43:25.592137+02
> (1 row)
>
> postgres=# select pg_stat_get_creation_time('xxx'::regclass);
> ERROR: internal function "pg_stat_get_creation_time" is not in
> internal lookup table
>
> It is expected and desired behave?

That error message has nothing to do with a pg_ prefix, as you would
find out yourself if you grepped for it. It means you created the
functional using language "internal", when you probably should have
used "c".

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-08-07 12:43:23 Re: WIP Patch: Use sortedness of CSV foreign tables for query planning
Previous Message Robert Haas 2012-08-07 12:39:09 Re: [PATCH] Docs: Make notes on sequences and rollback more obvious