Re: [Postgres-xc-bugs] [Postgres-xc-developers] Repairing Corrupt Objects

[West, W. <ww...@uc...>]

Koichi,

Yes it is related. I used your solution and it did rollback the long running prepared statement. I assumed this might have been causing an unregistered block on the table I was attempting to run queries against or vacuum. Unfortunately though this did not appear to alleviate the situation below. I have a single table affected by this. The other object in the database seem to work as expected. If I try to run a query against this table or vacuum it creates 2 pids like so:

505149   19636  0.0  0.0 192248  6824 ?        Ss   18:26   0:00 postgres: bigonc_prd bigonc 72.220.234.184(49302) VACUUM
505149   19889  0.0  0.0 191872  4992 ?        Ss   19:03   0:00 postgres: bigonc_prd bigonc 127.0.0.1(57250) VACUUM waiting

To me this looks like a process is pawned from the client while another process is started on the server. The client process seems to be causing a blocking like against the server pid. This is the output from PG_LOCKS for the client process:

“virtualxid" "3/324” "3/324” 19636 “ExclusiveLock” t t
“transactionid" “” 63030 "3/324” 19636 “ExclusiveLock” t f

Thanks for your help with the other issue as well,

Bill West

From: 鈴木 幸市 <ko...@in...<mailto:ko...@in...>>
Date: Monday, November 4, 2013 at 6:36 PM
To: William West <ww...@uc...<mailto:ww...@uc...>>
Cc: "pos...@li...<mailto:pos...@li...>" <pos...@li...<mailto:pos...@li...>>, "pos...@li...<mailto:pos...@li...>" <pos...@li...<mailto:pos...@li...>>
Subject: Re: [Postgres-xc-developers] Repairing Corrupt Objects

Is this related to the outstanding 2PC three days ago, which I responded with a solution?   If not, could you identify corrupt database object?

Regards;
---
Koichi Suzuki

On 2013/11/02, at 7:34, "West, William" <ww...@uc...<mailto:ww...@uc...>> wrote:

All,

Sorry for the multiple posting but the first emails seemed to get garbled. Hopefully this will post with the full text. Please ignore the other posts with this topic.

I have a database set up but it seems fairly unstable. I have a number of objects in the running database but I have one object that is corrupt. I know this because doing any query or dml statement on this table stalls the client. I also notice that when I run statements that encounter the invalid object. It spawns 2 process ID like below:

505149   19373  0.0  0.0 191768  5908 ?        Ss   10:30   0:00 postgres:  postgresql bigonc [local] VACUUM
505149   19379  1.2  0.0 191972 24776 ?        Ss   10:30   0:00 postgres: postgresql bigonc 127.0.0.1(46305) VACUUM waiting

These processes never complete and seem like they are locking one another. However there is nothing showing in pg_locks. Does anyone recognize this behavior. Is there anyway to repair or drop a corrupt object in the database?

Thanks,
Bill West
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk_______________________________________________
Postgres-xc-developers mailing list
Pos...@li...<mailto:Pos...@li...>
https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers