> The postmaster logs to a separate log file, but at the moment
> it's impossible to tell which sql comes from which connection.
> Is there an easy way to accomplish this?
>
The PID of the connected process is prepended to every log statement.
You can make use of this to know which sql comes from
Dear Ganesan,
pgautodoc (for dot output) + dot (from graphviz.org , creates
postscript) +
epssplit ( splits the postscript into multipage so that one can create
poster size
diagrams) works well for me.
I have 45 tables in the database though.
Regds
mallah.
Chris Travers wrote:
There is a fre
Hi,
I think yes.
I am running 7.4.1 and also using batchUpdate.
I am using this from http://jdbc.postgresql.org/download.html.
regards,
ivan.
beyaRecords - The home Urban music wrote:
> Hi,
> does anybody know whether the latest JDBC driver for postgreSQL 7.4.1
> supports batch updates?
>
> tha
Hi,
does anybody know whether the latest JDBC driver for postgreSQL 7.4.1
supports batch updates?
thanks in advance
Uzo
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAdd
Stef mentioned :
=> The postmaster logs to a separate log file, but at the moment
=> it's impossible to tell which sql comes from which connection.
=> Is there an easy way to accomplish this?
Erm... sorry ,
It appears my postgresql.conf is not an original. It didn't have
the log_pid option in. :)
Hi all,
I've switched on log_statement in postgresql.conf
for debugging purposes. I tried logging connections
and pids as well, but I need to match up the logged statements
to specific connections.
The postmaster logs to a separate log file, but at the moment
it's impossible to tell which sq
