Thanks will try these. Do you think I need to change the sync method for the
database? It is currently set to the default. I have an idea that the
problem could be that the connection is being used again to save another
large object when the database is shutdown and although we try to do a smart
shutdown if after 60 seconds postgres doesn't shutdown, we kill it and thus
could lose unsynched transactions.
Chris
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Tom Lane
Sent: Wednesday, April 09, 2003 2:45 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:
> How do I do that?
In 7.2 I believe what you want to turn on is debug_print_query, and
likely also log_timestamp and log_pid (unless you are logging to syslog,
which will supply those items for you). Don't forget to SIGHUP the
postmaster after you edit postgresql.conf.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)