Re: [Postgres-xc-general] Problem with taking database dump with pgxc-1.2.1

[Juned K. <jkh...@gm...>]

Hi Pavan,

Thanks a lot for your patch. its worked ;)
just tested out in local system, now just need to
apply it on server.

Regards,


On Thu, Apr 10, 2014 at 12:41 PM, Pavan Deolasee
<pav...@gm...>wrote:

>
> On Thu, Apr 10, 2014 at 12:29 PM, Juned Khan <jkh...@gm...> wrote:
>
>> Hi Masataka,
>>
>> Yeah you are correct, even pg_dumpall is not working.
>>
>
> This code in pg_dump.c seems to be source of the bug. Sorry, I don't have
> time right now to study it further and suggest a fix. As a temporary work
> around so that you can make progress, you can try compiling with the
> attached patch. This bug must be fixed in a saner way in the XC core though.
>
>     /*
>
>
>      * In Postgres-XC it is possible that the current value of a
>
>
>      * sequence cached on each node is different as several sessions
>
>
>      * might use the sequence on different nodes. So what we do here
>
>
>      * to get a consistent dump is to get the next value of sequence.
>
>
>      * This insures that sequence value is unique as nextval is directly
>
>
>      * obtained from GTM.
>
>
>      */
>
>     resetPQExpBuffer(query);
>
>     appendPQExpBuffer(query, "SELECT pg_catalog.nextval(");
>
> Thanks,
> Pavan
>
> --
> Pavan Deolasee
> http://www.linkedin.com/in/pavandeolasee
>



-- 
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com