|
From: Ashutosh B. <ash...@en...> - 2014-02-03 04:49:50
|
Hi Sandeep, Can you please check if similar error happens on vanilla PG. It may be an application + auto-vacuum error, which can happen in PG as well and might be harmless. It's auto-vacuum being cancelled. Auto-vacuum will run again during the next iteration. On Fri, Jan 31, 2014 at 11:21 PM, Sandeep Gupta <gup...@gm...>wrote: > Hi, > > I was debugging an outstanding issue with pgxc ( > http://sourceforge.net/mailarchive/forum.php?thread_name=CABEZHFtr_YoWb22UAnPGQz8M5KqpwzbviYiAgq_%3DY...@ma...&forum_name=postgres-xc-general). > > > I couldn't reproduce that error. But I do get this error. > > > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > LOG: sending cancel to blocking autovacuum PID 17222 > DETAIL: Process 13896 waits for AccessExclusiveLock on relation 16388 of > database 12626. > STATEMENT: drop index mdn > ERROR: canceling autovacuum task > CONTEXT: automatic analyze of table "postgres.public.la_directednetwork" > PreAbort Remote > > > It seems to be a deadlock issue and may be related to the earlier problem > as well. > Please let me know your comments. > > -Sandeep > > > > ------------------------------------------------------------------------------ > WatchGuard Dimension instantly turns raw network data into actionable > security intelligence. It gives you real-time visual feedback on key > security issues and trends. Skip the complicated setup - simply import > a virtual appliance and go from zero to informed in seconds. > > http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company |