| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: uptime function to postmaster |
| Date: | 2005-06-15 12:52:51 |
| Message-ID: | 200506151252.j5FCqpS14993@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Neil Conway wrote:
> Bruce Momjian wrote:
> > We need to preceed our function names with pg_ for cases like this where
> > we are supplying pg-specific behavior.
>
> We do? I'm not sure I can see much of a consistent naming convention for
> functions like these: version(), obj_description(), has_xyz_privilege(),
> format_type(), set_config(), and the like are surely "pg-specific", for
> example.
Yea, seems we aren't consistent.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerrit van Dyk | 2005-06-15 13:03:46 | Python setof patch |
| Previous Message | Pavel Stehule | 2005-06-15 12:31:10 | Re: user's exception PL/pgSQL |