| From: | Vick Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Perl script is killed by SIGPIPE |
| Date: | 2017-09-12 11:18:44 |
| Message-ID: | CALd+dce=18Ox2m45FBUBc87OBYazkbvw3TB+ByStGMS9AkD-uw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Sep 11, 2017 at 9:02 PM, Yogesh Sharma <yogeshraj95(at)gmail(dot)com>
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 "unexpected EOF on
> client connection" error is Comming.
> This issue is not Comming every time.
> We have found child script is killed by signal 13 SIGPIPE. When duplicate
> key violates error occured, script is killed but not all time.
>
>
I'm going to bet that the SIGPIPE is totally unrelated to having a
duplicate key violation. You will need to provide much more detail of what
you observe to figure this out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-12 12:01:02 | Re: Joining 16 tables seems slow |
| Previous Message | Pavel Stehule | 2017-09-12 11:13:58 | Re: Joining 16 tables seems slow |