Message-ID: <1473762821.896.1.camel@gmail.com>
Subject: Re: How to list ALL PostgreSQL functions?
From: jaime soler <jaime.soler@gmail.com>
Reply-To: jaime.soler@gmail.com
To: Poul Kristensen <bcc5226@gmail.com>, pgsql-admin@postgresql.org
Date: Tue, 13 Sep 2016 12:33:41 +0200
In-Reply-To: 
 <CAAOuvVrFc7y6DhLz8BbUVkT0iV+Z7zFU03S6CicxWJBf2N2HhA@mail.gmail.com>
References: 
	<CAAOuvVqoDPW=jysJOjXZLc8yLsHSa=QDpnLLTqYMYiK+yE=QRg@mail.gmail.com>
	 <38EB733C-FDF1-4644-ACC9-49D0CA125F79@simply.name>
	 <CAAOuvVqJEEyGQS0iyoobRK5YVK9yTEi6xLMASjNBNLvBad2wZA@mail.gmail.com>
	 <20160912105651.43vut4eeaxk25rg3@depesz.com>
	 <CAAOuvVpxhi3G+o65gi+BEaX3bYxQLZusQKx5S=WGMe2pD+9P+Q@mail.gmail.com>
	 <20160912112224.r4343jfzxiznoqpi@depesz.com>
	 <19291.1473681414@sss.pgh.pa.us>
	 <CAAOuvVrFc7y6DhLz8BbUVkT0iV+Z7zFU03S6CicxWJBf2N2HhA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

El lun, 12-09-2016 a las 20:00 +0200, Poul Kristensen escribió:
> 
> Thanks a lot.
> 
> How to size HW resources on a physical server for PG95+?

Please create a new thread and try to avoid mixing subjects 

> 
> What does PG95+ like? Cpu? L1(expensive I think) 2 or 3 cache level?.
> RAM?
> 
> Any idea?
> 
> Thanks
> 
> Poul
> 
> 
> 
> 2016-09-12 13:56 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
> > hubert depesz lubaczewski <depesz@depesz.com> writes:
> > > \df gives you list of user functions. you can add more
> > parameters, to
> > > limit/extend the list.
> > > like:
> > > \df pg_*
> > > will list all functions (including system one) that start with
> > pg_
> > > \dfS
> > > will list all system functions
> > > \df+ *xlog*
> > > will list all functions (including system) that contain "xlog" in
> > their
> > > name, with some additional columns, which include "description" -
> > one
> > > line info about the function.
> > 
> > Also, you can make your own queries on pg_proc, which is all that
> > psql is
> > doing here.  A nice abbreviated form is
> > 
> > select oid::regprocedure, obj_description(oid, 'pg_proc') from
> > pg_proc;
> > 
> > which gives you just the name, arg types, and comment for each row.
> > 
> > Keep in mind that
> > 
> > 1. This will show you an awful lot of stuff that's not meant to be
> > called
> > directly from SQL, eg I/O functions, operator implementation
> > functions,
> > aggregate support functions, cast functions, index support
> > functions.
> > I count 2831 rows in pg_proc in a virgin installation as of HEAD,
> > and
> > probably not even 1000 of them are really meant to be called as
> > functions
> > in ordinary queries.
> > 
> > 2. This will not show you some things that look like functions but
> > are
> > implemented by special grammar productions.  For that you'd have to
> > look into src/backend/parser/gram.y.
> > 
> >                         regards, tom lane
> > 
> 
> 
> -- 
> Med venlig hilsen / Best regards
> Poul Kristensen
> Linux-OS/Virtualizationexpert and Oracle DBA


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin