pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: raf <raf@raf.org>
To: pgsql-admin@postgresql.org
Subject: Re: getting 'full' names of functions?
Date: Thu, 5 Mar 2009 11:32:59 +1100
Message-ID: <20090305003259.GA24998@raf.org> (raw)
In-Reply-To: <20090304144122.153400@gmx.net>
References: <20090302122020.137490@gmx.net>
	<49ABE46D.3000501@synechron.com>
	<5521.1236006477@sss.pgh.pa.us>
	<20090304144122.153400@gmx.net>

Jan-Peter.Seifert@gmx.de wrote:

> Hello Ashish, Hello Tom,
> 
> thank you very much for your quick and helpful replies - I really appreciate that.
> 
> > > May be this will help you:
> > 
> > Easier is just
> > 	select oid::regprocedure from pg_proc where <whatever>
> 
> I guess I'll go with the very nifty type cast suggested by Tom though as this covers aggregate functions as well. This possibility should be mentioned in the docs - together with the system information functions http://www.postgresql.org/docs/8.3/interactive/functions-info.html
> 
> Too bad that this function syntax isn't part of information_schema.
> 
> Thank you very much to both of you.
> 

note that this method doesn't produce a complete function
signature. the precision and scale of numerics are not
included in the output. hopefully, that won't matter for
your needs.

cheers,
raf




view thread (10+ messages)  latest in thread

Message-ID: <20090305003259.GA24998@raf.org>
Permalink:  ../20090305003259.GA24998@raf.org/
Also on:    postgresql.org/message-id/20090305003259.GA24998@raf.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: raf@raf.org
  Subject: Re: getting 'full' names of functions?
  In-Reply-To: <20090305003259.GA24998@raf.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox