On Wed, Jan 28, 2009 at 2:10 AM, Abdul Rahman <abr_ora@yahoo.com> wrote:
> Thanks Jaime,
> Plz consider the actual log files to explore the issue in detail. Because I
> have pasted the log files of client machine, I am using (sorry).
>
>
> 2009-01-27 18:29:25 STATEMENT: delete from ci_cin_type_v where
> req_id='0824100207'
> delete from ci_cust_type_v where req_id='0824100207'
> delete from ci_dependents_v where req_id='0824100207'
> delete from ci_employer_v where req_id='0824100207'
> delete from ci_cor_sig_v where req_id='0824100207'
> delete from ci_corporate_v where req_id='0824100207'
> delete from ci_individual_v where req_id='0824100207'
> delete from ci_cif_v where req_id='0824100207'
then you have a lot of deletes, are there executing inside a
transaction? are you calling a trigger?
> 2009-01-27 18:29:41 ERROR: relation "ci_cust_type_v" does not exist
this table does not exist
> 2009-01-27 18:29:41 STATEMENT: delete from ci_cust_type_v where
> req_id='0824100207'
> 2009-01-27 18:52:08 LOG: could not receive data from client: No connection
> could be made because the target machine actively refused it.
> 2009-01-27 18:52:08 LOG: unexpected EOF on client connection
> 2009-01-27 18:52:08 LOG: could not receive data from client: No connection
> could be made because the target machine actively refused it.
> 2009-01-27 18:52:08 LOG: unexpected EOF on client connection
>
guess this messages are received after the CANCEL QUERY
if the series of deletes are all executed inside a transaction then
they all were rollback if not only the last one (the one that
generates the error) was rolledback
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
