From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | tesio(at)easynet(dot)fr |
Cc: | pgsql-general(at)hub(dot)org |
Subject: | Re: [GENERAL] Dirty workaround to get the results and the errors in the same output file |
Date: | 2000-01-11 13:26:20 |
Message-ID: | Pine.LNX.4.21.0001110101530.364-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
This sort of problem should be fixed in 7.0.
On 2000-01-10, Alain TESIO mentioned:
> Hello,
>
> Maybe you've experienced this problem too : when you have a huge
> script with an error somewhere, it's a pain to find out what
> line produced the error as you can't have the output of psql
> with the queries and the error message in the same file.
> I've tried psql ... 1>out 2>out, you the source queries at the
> top of the file, and the messages from psql at the bottom.
> Here's the trick which worked for me : replace stdout with
> stderr in psql.c, and compile again psql. When you got an error,
> the message is now just after the offending query.
>
> Alain
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
> ************
>
>
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | admin | 2000-01-11 13:38:09 | RE: [GENERAL] Memory leak in FreeBSD? |
Previous Message | admin | 2000-01-11 13:16:35 | Re: [GENERAL] Memory leak in FreeBSD? |