It is a setting in the postgresql.conf file. In 7.2 you set the
parameter debug_print_query to true (in 7.3 the parameter named changed
to log_statement)
--Barry
Chris White wrote:
> How do I do that?
>
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Wednesday, April 09, 2003 2:31 PM
> To: cjwhite@cisco.com
> Cc: pgsql-jdbc@postgresql.org; pgsql-admin@postgresql.org
> Subject: Re: [JDBC] [ADMIN] Problems with Large Objects using Postgres
> 7.2.1
>
>
> "Chris White" <cjwhite@cisco.com> writes:
>
>>The first and second are over the same connection. The third is over a
>>different connection, but issued after the second transaction has
>
> completed.
>
> Oh? At this point I'm prepared to bet that the second transaction isn't
> really committed when you think it is. Perhaps the "COMMIT" command
> isn't getting flushed out to the backend on time. You might want to
> turn on query logging and watch to see exactly what happens when.
>
> regards, tom lane
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
