Re: [GENERAL] Perl script is killed by SIGPIPE

2017-09-13 Thread tirveni yadav
On Wed, Sep 13, 2017 at 11:04 AM, Yogesh Sharma wrote: > Dear Daniel, > Yes , we are using DBI for connection. > > Basically we observed that after dbh->do() return nothing if we are trying > to insert duplicate entry. > But it is not occurred always. > It return exit 1 if

Re: [GENERAL] Perl script is killed by SIGPIPE

2017-09-12 Thread Yogesh Sharma
Dear Daniel, Yes , we are using DBI for connection. Basically we observed that after dbh->do() return nothing if we are trying to insert duplicate entry. But it is not occurred always. It return exit 1 if try to insert duplicate entry into Db. But sometime it return nothing and child script is

Re: [GENERAL] Perl script is killed by SIGPIPE

2017-09-12 Thread
> Daniel Verite wrote: > > Yogesh Sharma wrote: > > > We have found child script is killed by signal 13 SIGPIPE. When > > duplicate key violates error occured, script is killed but not all time. > > "child script" and this kind of error suggests that a forked process inherits > a database

Re: [GENERAL] Perl script is killed by SIGPIPE

2017-09-12 Thread Daniel Verite
Yogesh Sharma wrote: > We have found child script is killed by signal 13 SIGPIPE. When duplicate > key violates error occured, script is killed but not all time. "child script" and this kind of error suggests that a forked process inherits a database connection opened by a parent

Re: [GENERAL] Perl script is killed by SIGPIPE

2017-09-12 Thread Vick Khera
On Mon, Sep 11, 2017 at 9:02 PM, Yogesh Sharma wrote: > Dear All, > > > We have one perl script that is opening DB connection and performaing > insert DB operation.When duplicate entry Comming in query,Postgres > forecfully killing process itself and in Postgres log

[GENERAL] Perl script is killed by SIGPIPE

2017-09-11 Thread Yogesh Sharma
> > Dear All, We have one perl script that is opening DB connection and performaing insert DB operation.When duplicate entry Comming in query,Postgres forecfully killing process itself and in Postgres log "unexpected EOF on client connection" error is Comming. This issue is not Comming every