RE: Fastpath error on solaris 2.8 pgsql 7.1.3
От | chris markiewicz |
---|---|
Тема | RE: Fastpath error on solaris 2.8 pgsql 7.1.3 |
Дата | |
Msg-id | 009c01c12fb2$677612c0$77b846c6@cmarkiewicz обсуждение исходный текст |
Ответ на | Re: Fastpath error on solaris 2.8 pgsql 7.1.3 (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-jdbc |
Tom, When I say that this problem is erratic, I mean that sometimes a given piece of code works and sometimes it doesn't - not that some pieces work and some don't (don't know if that helps). How is a BEGIN indicated? I get a Connection, grab a Statement from it, and run my query. Do I have to do anything special to tell Fastpath that I am BEGINning a transaction? Thanks chris -----Original Message----- From: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Tom Lane Sent: Monday, August 27, 2001 4:43 PM To: T.R.Missner@level3.com Cc: pgsql-jdbc@postgresql.org Subject: Re: [JDBC] Fastpath error on solaris 2.8 pgsql 7.1.3 T.R.Missner@Level3.com writes: > FastPath call returned ERROR: lo_write: invalid large obj descriptor (0) Usually this indicates that you didn't have the lo_open ... lo_write ... lo_close sequence wrapped in a transaction block (BEGIN/COMMIT SQL commands). Since it's erratic for you, I'd bet that some of your application control paths have the BEGIN and some don't. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
В списке pgsql-jdbc по дате отправления: