| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Joseph S <jks(at)selectacast(dot)net> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Lots of junk on my console |
| Date: | 2007-03-29 21:13:26 |
| Message-ID: | Pine.BSO.4.64.0703291711450.27198@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 29 Mar 2007, Joseph S wrote:
> Joseph S wrote:
>> I append ?loglevel=1 to the db connection urls I use for running VACUUM
>> commands. Would that set the logwriter?
>>
> Actually I see that it does. The comment in AbstractJdbc2Connection reads:
>
> // Read loglevel arg and set the loglevel based on this value;
> // In addition to setting the log level, enable output to
> // standard out if no other printwriter is set
>
> So I guess I have to set it back to null each time I create a db connection.
>
Perhaps you should avoid using loglevel=1 if you don't want any logging
output. If you want to get VACUUM details that should be available in a
SQLWarning attached to the statement and should be easier to put where you
want than something that is dumped to stdout.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2007-03-29 21:16:42 | Re: [JDBC] problems with plan invalidation |
| Previous Message | Joseph S | 2007-03-29 20:55:07 | Re: Lots of junk on my console |