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

[Koichi S. <koi...@gm...>]

The fix will be okay for the short term basis.   At present, sequence
is handled by GTM and we need to invoke nextval() to get its value,
which advances current sequence value, which may not be comfortable
for one usecase.   This is the main reason why XC's pg_dump and
pg_dumpall do not work in read-only transaction.

We need this fix after this.

Regards;
---
Koichi Suzuki


2014-04-10 15:59 GMT+09:00 Juned Khan <jkh...@gm...>:
> Hi Masataka,
>
> Yeah you are correct, even pg_dumpall is not working.
> do you have any idea about how to solve this issue or any
> alternative way to take dump ?
>
>
> Regards,
>
>
> On Thu, Apr 10, 2014 at 12:26 PM, Masataka Saito <pg...@gm...> wrote:
>>
>> I can't believe pg_dumpall is working.
>>
>> pg_dumpall uses pg_dump internally to dump each database. pg_dump uses
>> nextval() to obtain sequce values in a read only transaction. It's
>> invalid operation because nextval() changes a sequce value regardless
>> of being read-only transaction.
>>
>> Regards.
>>
>> On 9 April 2014 17:43, 鈴木 幸市 <ko...@in...> wrote:
>> > Please try pg_dumpall if it works.
>> >
>> > Regards;
>> > ---
>> > Koichi Suzuki
>> >
>> > 2014/04/09 17:31、Juned Khan <jkh...@gm...> のメール：
>> >
>> > Hi All,
>> >
>> > recently i have just installed the pgxc-1.2.1 on one of my production
>> > server
>> > but when i tried to take backup of all data it gave me below errors.
>> >
>> > PGXC pg_dump mydatabase > mydatabase.sql
>> > pg_dump: [archiver (db)] query failed: ERROR:  cannot execute nextval()
>> > in a
>> > read-only transaction
>> > pg_dump: [archiver (db)] query was: SELECT
>> > pg_catalog.nextval('account_package_id_seq');
>> >
>> > With some googling i found this
>> >
>> > http://www.postgresql.org/message-id/4DC...@po...
>> >
>> > How to solve this issue? even pg_dumpall is working
>> >
>> > Please suggest.
>> >
>> > --
>> >
>> > Thanks,
>> > Juned Khan
>> > iNextrix Technologies Pvt Ltd.
>> > www.inextrix.com
>> >
>> > ------------------------------------------------------------------------------
>> > Put Bad Developers to Shame
>> > Dominate Development with Jenkins Continuous Integration
>> > Continuously Automate Build, Test & Deployment
>> > Start a new project now. Try Jenkins in the cloud.
>> >
>> > http://p.sf.net/sfu/13600_Cloudbees_______________________________________________
>> > Postgres-xc-general mailing list
>> > Pos...@li...
>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >
>> >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Put Bad Developers to Shame
>> > Dominate Development with Jenkins Continuous Integration
>> > Continuously Automate Build, Test & Deployment
>> > Start a new project now. Try Jenkins in the cloud.
>> > http://p.sf.net/sfu/13600_Cloudbees
>> > _______________________________________________
>> > Postgres-xc-general mailing list
>> > Pos...@li...
>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>> >
>
>
>
>
> --
> Thanks,
> Juned Khan
> iNextrix Technologies Pvt Ltd.
> www.inextrix.com
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>