| From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "David BOURIAUD" <david(dot)bouriaud(at)ac-rouen(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: One more option for pg_dump... |
| Date: | 2008-02-27 03:41:30 |
| Message-ID: | 37ed240d0802261941g1d46e637nc56a6a0c748ffcff@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 27, 2008 at 2:29 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> > You could just pull up a psql session and do a "select
> > pg_func_def(regproc);" and there you go, one fully formed CREATE
> > FUNCTION statement.
>
> \df+ function(type)
>
Sure, if your idea of a good time is looking at the output of \df+,
and then querying pg_proc anyway to find out whether the function is
strict or not, and then writing out a CREATE FUNCTION by hand. \df+
is great for getting a quick idea of what functions are available and
what they do. For producing executable SQL to re-create those
functions, it's a mess.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-27 04:46:54 | Re: An idea for parallelizing COPY within one backend |
| Previous Message | Joshua D. Drake | 2008-02-27 03:29:55 | Re: One more option for pg_dump... |