postgres-xc-general Mailing List for Postgres-XC (Page 2)

Thanks a lot for the report.

Could you let me know if you got this message while handling replicated
table or distributed table?

Most probable case is inconsistency in replicated table's replica.   Before
looking into it, could you check if there's no outstanding 2PC transactions
in your datanodes.   Even though you don't issue 2PC commands, XC may issue
it internally when more than one node are involved in updating transactions
and you may have such outstanding 2PC transactions especially when some
node fails (did you have such failure?).

You can check this by selecting pg_prepared_statements catalog.   This
catalog is local to each coordinator and datanode so you should issue
select statement using EXECUTE DIRECT statement.   If you find such
outstanding 2PC transactions, you can rollback them as follows:

1. Connect psql directly to a target datanode/coordinator as a superuser.
2. Issue "SET xc_maintenance_mode to ON" to enable local manual repair.
3. Issue ROLLBACK PREPARED statement to rollback such outstanding 2PCs.
4. Repeat 1 to 3 for all the coordinator/datanodes which contains such
outstanding 2PCs.

Postgres-XC provides pgxc_clean utility to do the above step.   This will
be found in contrib directory of the source tarball.

If you don't have such outstanding 2PC transactions or you still have the
same error, please try the following.

If you are handling replicated tables, we have a chance that there's some
inconsistencies in each replica.   To check this, use "EXECUTE DIRECT"
statement to visit each datanode and check if all the replica are
identical.   If not, you can recover damaged tuples as follows:

1. Connect psql directly to a target datanode as a superuser.
2. Issue "SET xc_maintenance_mode to ON" to enable local manual repair.
3. Issue SQL statement to repair damaged tuples.
4. Repeat 1 to 3 for all the damaged datanode.

If you've got the error while handling distributed tables, there could be
another error cause.   I need to analylze the case more in detail.   Please
let me know if you are handling distributed tables.

Best Regards;

---
Koichi Suzuki


2013/11/6 Alex Hudson <ale...@au...>

> Hi guys,
>
>
>
> I’m working in an application using php and Postgrexc clustered.
>
> In the event of save some information, the app shows me the following
> lines:
>
>
>
> Application raised an exception class <b>ADODB_Exception</b> with message
> <b>'postgres7 error: [-1: ERROR:  consistency check on SPI tuple count
> failed
>
>
>
> Why produces this error? How can i fix it? May be because I’m using
> encoding LATIN1?
>
>
>
> Thanks and regards,
>
>
>
> Alex Hudson S.
>
>
>
>
> ------------------------------------------------------------------------------
> 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-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>

Hi guys,

 

I'm working in an application using php and Postgrexc clustered.

In the event of save some information, the app shows me the following lines:

 

Application raised an exception class <b>ADODB_Exception</b> with message
<b>'postgres7 error: [-1: ERROR:  consistency check on SPI tuple count
failed

 

Why produces this error? How can i fix it? May be because I'm using
encoding LATIN1?

 

Thanks and regards,

 

Alex Hudson S.