Re: [GENERAL] How to echo statements in sourced file?

2008-12-04 Thread Kynn Jones
Thank you all.  From your replies I was able to figure out what I needed:
\set ECHO queries
Kynn


On Wed, Dec 3, 2008 at 7:14 PM, Kynn Jones [EMAIL PROTECTED] wrote:

 Hi.  I have a collection of SQL statements stored in a file that I run
 periodically via cron.  Running this script takes a bit too long, even for
 a cron job, and I would like to profile it.
 I learned from Andreas Kretschmer (in another thread, in the
 pgsql-performance list) about the \timing directive, which is useful for
 this.

 Now, after turning timing on, when I source the script from within psql,
 with

 mydb= \i /path/to/my/script

 ...I get output lines like this

 Time: 38.519 ms

 right in my psql terminal after each statement in the file gets executed.

 But now I need a way to have these statements that are being timed
 themselves echoed to the terminal.  Is there a way to do this?

 TIA!

 Kynn




Re: [GENERAL] How to echo statements in sourced file?

2008-12-03 Thread Alvaro Herrera
Kynn Jones escribió:

 But now I need a way to have these statements that are being timed
 themselves echoed to the terminal.  Is there a way to do this?

psql -e

-- 
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

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


Re: [GENERAL] How to echo statements in sourced file?

2008-12-03 Thread Harvey, Allan AC

 

right in my psql terminal after each statement in the file gets executed.


But now I need a way to have these statements that are being timed themselves 
echoed to the terminal.  Is there a way to do this?


 

start psql with the -a switch, I think.
 
Allan


The material contained in this email may be confidential, privileged or 
copyrighted. If you are not the intended recipient, use, disclosure or copying 
of this information is prohibited. If you have received this document in error, 
please advise the sender and delete the document. Neither OneSteel nor the 
sender accept responsibility for any viruses contained in this email or any 
attachments.