Problems with postgres V6.5.3 large objects

Поиск
Список
Период
Сортировка
От Charles Randle
Тема Problems with postgres V6.5.3 large objects
Дата
Msg-id 384ACD0B.2491AFBE@cybervale.com
обсуждение исходный текст
Ответы Re: [INTERFACES] Problems with postgres V6.5.3 large objects  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [INTERFACES] Problems with postgres V6.5.3 large objects  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-interfaces
Hi all, <p>I'm  relatively new to postgres amd I'm attempting to use  large objects to store and play-back messages
directlyfrom the database . I have a number of problems/questions/issues : <p>1) Whenever I try to open more than one
largeobject within my class (I'm using C++)  The following message appears in the postgres backend log-file &  the
applicationterminates .<font color="#3366FF"></font><p><font color="#000000">"query: SELECT message_data FROM
receptormessagesWHERE message_name = 'wait_mess</font><br /><font color="#000000">age_one'</font><br /><font
color="#000000">ProcessQuery</font><br/><font color="#000000">CommitTransactionCommand</font><br /><font
color="#000000">StartTransactionCommand</font><br/><font color="#000000">ERROR:  update_fp_info: cache lookup for
function1 failed</font><br /><font color="#000000">AbortCurrentTransaction</font><br /><font color="#000000">FATAL 1: 
Socketcommand type</font><br /><font color="#000000">proc_exit(0) [#0]"</font><br /><font color="#000000"> </font><br
/>   Note 1) - Note that the Oids for the  large objects are stored in a table called 'receptormessages' <br
/>             2) - The transaction necessary for the access to the large objects begins in the constructor of <br
/>                     the class and terminates of the object is ever destroyed (in the destructor). <br />  <p>2) I am
thinkingof using the libpq++ interface to access the large objects , However from what I've seen each instance of the
classwould create a new connection to the backend , from the same process ! <br />        a) How expensive is this
multipleconnection option given that many large objects may be in use <br />             at any one time  ? <br
/>       b) If this option is expensive , is there any way to access many large objects  and only have <br
/>            one connection to the database  with the C++ interface to these objects ? <br />  <p>Regards, <br
/>CharlesRandle. <p>  <br />  <br />  

В списке pgsql-interfaces по дате отправления:

Предыдущее
От: Balajee Shrikanth
Дата:
Сообщение: Problems after creating jdbc driver postgresql.jar 6.5.3
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [INTERFACES] Problems with postgres V6.5.3 large objects