[Postgres-xl-general] ERROR: could not find tuple for relation

Dennis dennisr at visi.com
Sun Oct 5 08:01:26 PDT 2014


Hi thanks for the offer to help.

I am running with code from GIT repo that I pulled on about August 14.  I will do a new pull and rebuild the bins, I was considering that as well after seeing Pavan’s post this past week.

I am running with gtm_proxy so I will try running without the proxies running.  What are the down sides to not having the proxies running? Just curious on that point. 

Autovacuum is enabled, I will try running with it turned off if patching the code does not help as well.

Looking at the gtm logs I am seeing quite a few lines like these, I have also attached the full gtm log:

1:140414401500928:2014-10-03 23:12:09.250 CDT -WARNING:  No transaction handle for gxid: 48201
LOCATION:  GTM_GXIDToHandle, gtm_txn.c:175
1:140414401500928:2014-10-03 23:12:09.250 CDT -WARNING:  Invalid transaction handle: -1
LOCATION:  GTM_HandleToTransactionInfo, gtm_txn.c:225
1:140414401500928:2014-10-03 23:12:30.272 CDT -WARNING:  No transaction handle for gxid: 48201
LOCATION:  GTM_GXIDToHandle, gtm_txn.c:175
1:140414401500928:2014-10-03 23:12:30.272 CDT -WARNING:  Invalid transaction handle: -1
LOCATION:  GTM_HandleToTransactionInfo, gtm_txn.c:225
1:140414370031360:2014-10-03 23:24:18.479 CDT -WARNING:  No transaction handle for gxid: 48242
LOCATION:  GTM_GXIDToHandle, gtm_txn.c:175
1:140414370031360:2014-10-03 23:24:18.480 CDT -WARNING:  Invalid transaction handle: -1
LOCATION:  GTM_HandleToTransactionInfo, gtm_txn.c:225
1:140414370031360:2014-10-03 23:24:38.500 CDT -WARNING:  No transaction handle for gxid: 48242
LOCATION:  GTM_GXIDToHandle, gtm_txn.c:175






On Oct 4, 2014, at 12:46 PM, Mason Sharp <msharp at translattice.com> wrote:

> 
> 
> On Sat, Oct 4, 2014 at 1:33 AM, Dennis <dennisr at visi.com> wrote:
> I keep running into this problem below when creating indexes.  It doesn’t happen all the time and I am having trouble repeating it.
> 
> CREATE INDEX
> ERROR:  could not find tuple for relation 533283
> CREATE INDEX
> ERROR:  could not find tuple for relation 532752
> CREATE INDEX
> ERROR:  could not find tuple for relation 533290
> ERROR:  could not find tuple for relation 532756
> ERROR:  could not find tuple for relation 532703
> CREATE INDEX
> ERROR:  could not find tuple for relation 532885
> CREATE INDEX
> ERROR:  could not find tuple for relation 532753
> ERROR:  could not find tuple for relation 532754
> 
> The process that I using is as follows:
> 1. Load ~1TB database using copy command (I have about 12 tables and I load them concurrently)
> 2. Create primary keys
> 3. Load/create 67 indexes on the 12 tables. I am running multiple create statements simultaneously using GNU parallel.
> 
> I am not vacuuming between the load and the index creations. 
>  
> 
> I am not able to find much in my log files indicating what the problem is.
> 
> Anyone have suggestions as to what the problem might be or how to better diagnose the issue?
> 
> Sure, let's try to isolate the issue. The error message is concerning.  
> 
> The GTM log is fairly verbose, but did you take a look at that as well?
> 
> Are you running with the latest code? Or the RPM based one? Are you using GTM Proxy as part of your configuration? If so, does the error disappear if you do not use it? Pavan Deolasee is currently fixing some issues he discovered related to GTM proxy, it may be related to that. He recently posted a patch. You could also try with that patch to see if it helps.
> 
> Also, is autovacuum turned on? If, after looking at GTM Proxy, you are still having issues, please try turning off autovacuum on the datanodes to see if that affects things. If using recent development code, while it addresses some bugs, perhaps an issue was introduced.
> 
> Please keep me updated, I want to make sure that this gets addressed. I know you mentioned that it is difficult to reproduce, so any info is appreciated.
> 
> Thanks,
> 
> Mason

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20141005/319acc3f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gtm.log.gz
Type: application/x-gzip
Size: 6466 bytes
Desc: not available
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20141005/319acc3f/attachment.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/pipermail/postgres-xl-general-postgres-xl.org/attachments/20141005/319acc3f/attachment-0001.htm>


More information about the postgres-xl-general mailing list