Ok, I was able to log the postgres.log and I found the entire query. I am very sorry for causing this confusion. The way the query was being submitted made it look like it was being cut off, and our daily log files are multi-gig so mining them is quite a pain. (Also, I was quite under the weather yesterday). Anyway, it good to know there are some possible options besides always mining the logs. Thanks, Chris On 8/16/05, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > adey <adey11@xxxxxxxxx> writes: > > You could try the following query after enabling the > > stats_command_string parameter in the postgresql.conf file:- > > The pg_stat_activity mechanism *does* have a limit on the query > string length it can display, and if memory serves that limit was > not large in 7.3.* --- I'm thinking 256 bytes. > > However, the postmaster log doesn't have any hard limit that I'm > aware of, so it seems like Chris' original approach should work. > > regards, tom lane >
