From: Ashutosh B. <ash...@en...> - 2013-04-24 14:04:42
|
Good, that works. This bug is causing testcase truncate to fail. On Wed, Apr 24, 2013 at 6:53 PM, Nikhil Sontakke <ni...@st...>wrote: > Hi Ashutosh, > > By the EOW? > > Regards, > Nikhils > > > > On Wed, Apr 24, 2013 at 6:49 PM, Ashutosh Bapat < > ash...@en...> wrote: > >> Hi Nikhil, >> Thanks for taking this up? >> >> By when do you think you can provide the patch? >> >> >> On Wed, Apr 24, 2013 at 6:01 PM, Nikhil Sontakke <ni...@st...>wrote: >> >>> >>> >>> >>> >>>> ResetSequence(), the function being called from ExecuteTruncate() does >>>> not send reset message to GTM. It applies sequence changes locally on the >>>> coordinator, which is not enough. >>>> >>>> Can someone with relevant experience look into this problem and provide >>>> a fix? >>>> >>>> I have attached the testcase and its output showing the bug. >>>> >>>> >>> I guess setval() was handled but we forgot to handle reset sequence. I >>> will take this up when I cleanup currval, nextval for negative sequences. >>> >>> Regards, >>> Nikhils >>> >> >> >> >> -- >> Best Wishes, >> Ashutosh Bapat >> EntepriseDB Corporation >> The Postgres Database Company >> > > > > -- > StormDB - http://www.stormdb.com > The Database Cloud > -- Best Wishes, Ashutosh Bapat EntepriseDB Corporation The Postgres Database Company |