Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAB0yrekxKSWZKc_YSyhtmsO5UPj8VGqV0da9YhrOuS-7Vc_W-w@mail.gmail.com>
References: <CA+-yw=JOF1iiYC9A5oUKsYhFy827YV7XcgDyb77WfBG0AX8Gzg@mail.gmail.com>
 <CAFht1hJAZ72xa2+Ceg7X4pTAPCXXVgv+BMADgZDf-dg1QN1z9A@mail.gmail.com> <CAB0yrekxKSWZKc_YSyhtmsO5UPj8VGqV0da9YhrOuS-7Vc_W-w@mail.gmail.com>
From: "Alex (Oleksandr) Diachenko" <odiachenko@pivotal.io>
Date: Tue, 14 Feb 2017 18:13:30 -0800
Message-ID: <CA+-yw=JMpEkvXuQHWzw_gHVUHH+PFNN+zL7qh=b+xDSLaTPGTA@mail.gmail.com>
Subject: Re: HAWQ upgrade command
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a113f42040fbc880548883a42
archived-at: Wed, 15 Feb 2017 02:13:39 -0000

--001a113f42040fbc880548883a42
Content-Type: text/plain; charset=UTF-8

Hi Lili and Hubert,

I was testing my changes to upgrade HAWQ from HDB 2.0.0.0 to
HDB-2.2.0.0(current master), with my changes in the scope of HAWQ-1314.
It went through, so no worries.

Regards, Alex.

On Sun, Feb 12, 2017 at 7:35 PM, Hubert Zhang <hzhang@pivotal.io> wrote:

> Hi Alex,
>   There is an known issue if you init the system between commit 787c096 and
>  commit 1866a93(Nov 22-Nov25 2016). Could you please check the proargtypes
> of function gp_relfile_insert_for_register in pg_proc by the following
> steps:
>
>    - select oid,* from pg_proc where proname
>    ='gp_relfile_insert_for_register';
>    - \c template1
>    - select oid,* from pg_proc where proname
>    ='gp_relfile_insert_for_register';
>
>
> On Mon, Feb 13, 2017 at 10:57 AM, Lili Ma <lma@pivotal.io> wrote:
>
> > Hi Alex,
> >
> > Could you tell the original version and to-be-upgraded version of HAWQ,
> so
> > that we can try to reproduce it?
> >
> > Thanks
> > Lili
> >
> > On Sat, Feb 11, 2017 at 10:27 AM, Alex (Oleksandr) Diachenko <
> > odiachenko@pivotal.io> wrote:
> >
> > > Hi,
> > >
> > > I saw HAWQ-1171 was merged to master recently, and I am trying to
> figure
> > > out how it works.
> > > The scripts drops gp_relfile_insert_for_register procedure if it exists
> > and
> > > creates it again using latest signature.
> > >
> > > I tried it out and it worked for me in a case when
> > > gp_relfile_insert_for_register doesn't exist.
> > > But in case when gp_relfile_insert_for_register exist I am getting:
> > >
> > > *ERROR:  cannot drop function
> > > gp_relfile_insert_for_register(oid,oid,oid,oid,oid,
> > > cstring,character,character,oid)
> > > because it is required by the database system*
> > >
> > > Is it even intended to be run when procedure exists? Do I have to set
> any
> > > GUCs to make it work?
> > >
> > > Regards, Alex.
> > >
> >
>
>
>
> --
> Thanks
>
> Hubert Zhang
>

--001a113f42040fbc880548883a42--