From: | nolan(at)celery(dot)tssi(dot)com |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian), pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Updating psql for features of new FE/BE protocol |
Date: | 2003-06-26 07:06:34 |
Message-ID: | 20030626070634.30787.qmail@celery.tssi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> This is irrelevant to what I'm doing, in any case, and it's not an itch
> I feel personally. Work on it yourself if you want it ...
OK, I figured it out. :-)
It's a fairly short patch in 7.3.3, what do I need to do to submit it
for 7.4?
I also made a minor functional change that may need to be turned into
an additional variant on echo: if ECHO is set to 'queries' and output
is being sent other than to stdout (\o), it echoes the query to the output
file or pipe.
If that's too much of a change and this needs to be a separate option,
I'd suggest something like setting ECHO to 'queryout'. To be complete,
would it need to have a command line equivalent, too?
BTW, I figured out how to direct the output to a separate file each time,
I put the following in .psqlrc:
\o |tee `echo psql_${$}.txt`
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-06-26 08:21:02 | date parsing |
Previous Message | Joe Conway | 2003-06-26 05:13:16 | Re: [HACKERS] allowed user/db variables |