Re: getpid() function - Mailing list pgsql-hackers

From Karel Zak
Subject Re: getpid() function
Date
Msg-id 20020802102636.A4278@zf.jcu.cz
Whole thread Raw
In response to Re: getpid() function  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: getpid() function  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
On Thu, Aug 01, 2002 at 01:41:49PM -0400, Bruce Momjian wrote:
> 
> Added to TODO:
> 
>     * Consistently name server-side internal functions
OK, good start of discussion is define groups of the PostgreSQL functions:
1/ Extern compatible functions
    The functions compatible with standards or customs    or others SQL servers. For example trim, to_char, ...    2/
PostgreSQLspecific functions used in standard SQL operations   (the function works with standard data and not load it
from   internal PostgreSQL stuff).
 
   For example convert(), all datetype function like int(). The name    convenition must be like names in group 1/
3/ PostgreSQL specific system functions
   For example pg_backend_pid(). IMHO clean solution is   use "pg_" prefix.
4/ The calls without '( )'
   For example "SELECT current_user;" IMHO right is not use   "pg_" prefix _if_ you call it without braces. _But_ if
youcall   it with '()' and function can be member of group 3/ is right use   "pg_" prefix.
 
   For example:       SELECT current_user;       SELECT pg_current_user();
5/ Deprecated functions
   In docs marked as "deprecated" and will removed in some major   release (for example in 8.0).

6/ ???

-- Karel Zak  <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz,
http://mape.jcu.cz


pgsql-hackers by date:

Previous
From: Curt Sampson
Date:
Subject: Re: Why is MySQL more chosen over PostgreSQL?
Next
From: Tatsuo Ishii
Date:
Subject: Re: getpid() function