| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | stafford(at)marine(dot)rutgers(dot)edu |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: pl/pgSQL development environment |
| Date: | 2008-08-04 23:09:10 |
| Message-ID: | 14500.1217891350@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Wm.A.Stafford" <stafford(at)marine(dot)rutgers(dot)edu> writes:
> ... Using both psql and pgADMINIII I was able to load and execute this and
> see 2 as the output but I did not
> see the output of the RAISE statement. The RAISE output was not in the
> log file either.
> Where does it go and can it be redirected to stdout?
In addition to the other comments: client_min_messages can be adjusted
if you want to get DEBUG-level messages on the client side. (I'm not
sure how well that works in pgAdmin, but it definitely works in psql.)
Realize though that you'll get chatter from built-in DEBUG output too,
whether you are sending it to the log or the client. It might be better
to use a higher message level for temporary debugging messages in
plpgsql functions. I tend to use NOTICE myself.
> Since pl/pgSQL does not have packages, what is the usual way of managing
> groups of related functions and procedures.
About all you can do at the moment is put them all into a schema.
There has been some talk of creating a "module" facility in future
PG releases, but nothing's happened beyond talk, yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Selvakaruppiah s-TLS,Chennai | 2008-08-05 02:54:00 | SetQueryTimeout in Postgres 8.1.4 |
| Previous Message | Charles N. Charotti | 2008-08-04 20:13:11 | Re: pl/pgSQL development environment |