Re: [ADMIN] Problems with Large Objects using Postgres 7.2.1
От | Chris White |
---|---|
Тема | Re: [ADMIN] Problems with Large Objects using Postgres 7.2.1 |
Дата | |
Msg-id | 013501c2fee0$bb42ecd0$ff926b80@amer.cisco.com обсуждение исходный текст |
Ответ на | Re: [ADMIN] Problems with Large Objects using Postgres 7.2.1 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [ADMIN] Problems with Large Objects using Postgres 7.2.1
Re: [ADMIN] Problems with Large Objects using Postgres 7.2.1 |
Список | pgsql-jdbc |
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
В списке pgsql-jdbc по дате отправления: