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

[Aaron J. <aja...@re...>]

So, I tried the same thing and applied this patch.  I even verified that it was setting the transaction mode to "serializable, read only, deferrable" - yet the problem persists.  I believe my execution is similar to the OP.

pg_dump -d analysisdb --serializable-deferrable

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('customtype_customtypeid_seq');

Did I miss something else?

Aaron

________________________________
From: Juned Khan [jkh...@gm...]
Sent: Friday, April 11, 2014 2:05 AM
To: Pavan Deolasee
Cc: Postgres-XC mailing list
Subject: Re: [Postgres-xc-general] Problem with taking database dump with pgxc-1.2.1

Thanks to Pavan and Koichi for your inputs.

So i think as of now i do not need to worry about
this




On Fri, Apr 11, 2014 at 12:31 PM, Pavan Deolasee <pav...@gm...<mailto:pav...@gm...>> wrote:
On Fri, Apr 11, 2014 at 12:07 PM, Juned Khan <jkh...@gm...<mailto:jkh...@gm...>> wrote:
As of now this fix worked fine for me. is there any side effect of this
patch ?

IMV there won't be any significant side effect of the patch. pg_dump used to run in RW mode till we fixed it in 9.3.  If it has worked for so many years, it may work for some more time too :-) Marking pg_dump READ ONLY was exactly to catch bugs like these. But other than that, I think its OK.

Thanks,
Pavan

--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee



--
Thanks,
Juned Khan
iNextrix Technologies Pvt Ltd.
www.inextrix.com<http://www.inextrix.com/>