On 10/15/18 8:10 AM, Shrikant Bhende wrote:
Hi Adrain,
Its running on the local machine itself. I googled this around but most of the blog says that stop supporting the older version, also I took pg_dumpall from EDB PPAS cluster using PostgreSQL binaries, if that might have caused anything.

The data looks alright, this is a client(psql) issue. So:

1) Which psql are you using the EDB or community one?

2) What is the exact psql command you are using?



Thanks.

On Mon, Oct 15, 2018 at 8:36 PM Adrian Klaver <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>> wrote:

    On 10/15/18 8:04 AM, Shrikant Bhende wrote:
     > Hi Adrian,
     >
     > There is no explicit client its just simple restore using psql
    with all
     > default settings required.

    psql is the client. Where is it running relative to the server locally
    or remote?

     >
     > On Mon, Oct 15, 2018 at 6:50 PM Adrian Klaver
    <adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
     > <mailto:adrian.kla...@aklaver.com
    <mailto:adrian.kla...@aklaver.com>>> wrote:
     >
     >     On 10/15/18 5:36 AM, Shrikant Bhende wrote:
     >      > Hi Team,
     >      >
     >      > I am trying to restore the backup into postgresql 9.6 and
    during
     >     restore
     >      > copy command fails with below error,
     >      >
     >      > 2018-10-12 06:21:40 UTC [40407]: [28-1]
     >      > application=psql.bin,user=postgres,db=cloudLOG:  could not
    send
     >     data to
     >      > client: Broken pipe
     >
     >     I would say the above is the issue.
     >
     >     Where is the client running relative to the server?
     >
     >      > 2018-10-12 06:21:40 UTC [40407]: [29-1]
     >      > application=psql.bin,user=postgres,db=cloudSTATEMENT:  COPY
     >      > d20160905_x_20da999ef9434e60942859c3690e642f (did,
    location_id, h00,
     >      > h00_min, h00_max, h00_wgt, h01, h01_min, h01_max, h01_wgt,
    h02,
     >     h02_min,
     >      > h02_max, h02_wgt, h03, h03_min, h03_max, h03_wgt, h04,
    h04_min,
     >     h04_max,
     >      > h04_wgt, h05, h05_min, h05_max, h05_wgt, h06, h06_min,
    h06_max,
     >     h06_wgt,
     >      > h07, h07_min, h07_max, h07_wgt, h08, h08_min, h08_max,
    h08_wgt, h09,
     >      > h09_min, h09_max, h09_wgt, h10, h10_min, h10_max, h10_wgt,
    h11,
     >     h11_min,
     >      > h11_max, h11_wgt, h12, h12_min, h12_max, h12_wgt, h13,
    h13_min,
     >     h13_max,
     >      > h13_wgt, h14, h14_min, h14_max, h14_wgt, h15, h15_min,
    h15_max,
     >     h15_wgt,
     >      > h16, h16_min, h16_max, h16_wgt, h17, h17_min, h17_max,
    h17_wgt, h18,
     >      > h18_min, h18_max, h18_wgt, h19, h19_min, h19_max, h19_wgt,
    h20,
     >     h20_min,
     >      > h20_max, h20_wgt, h21, h21_min, h21_max, h21_wgt, h22,
    h22_min,
     >     h22_max,
     >      > h22_wgt, h23, h23_min, h23_max, h23_wgt) FROM stdin;
     >      > 2018-10-12 06:21:40 UTC [40407]: [30-1]
     >      > application=psql.bin,user=postgres,db=cloudFATAL: terminating
     >     connection
     >      > because protocol synchronization was lost
     >      >
     >      > I am trying to migrate the DB from EDB PPAS to community
     >     PostgreSQL, we
     >      > don't have any oracle or PPAS dependent objects so I took the
     >     pg_dumpall
     >      > using the PostgreSQL binaries and trying to restore the same.
     >      >
     >      > PPAS :: 9.3
     >      > PostgreSQL : 9.6
     >      > O/S :: Centos 6.6
     >      >
     >      > Thanks and Regards.
     >      >
     >      > --
     >      > Shrikant Bhende
     >      > +91-9975543712
     >
     >
     >     --
     >     Adrian Klaver
     > adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>
    <mailto:adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>>
     >
     >
     >
     > --
     > Shrikant Bhende
     > +91-9975543712


-- Adrian Klaver
    adrian.kla...@aklaver.com <mailto:adrian.kla...@aklaver.com>



--
Shrikant Bhende
+91-9975543712


--
Adrian Klaver
adrian.kla...@aklaver.com

Reply via email to