From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> |
Cc: | John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, "<postgres-xc-general(at)lists(dot)sourceforge(dot)net>" <postgres-xc-general(at)lists(dot)sourceforge(dot)net> |
Subject: | Re: [Postgres-xc-general] "Tuple not found error" during Index creation |
Date: | 2013-12-11 04:23:47 |
Message-ID: | CAB7nPqQXhBj2TS3=3FA3FtvrFXiszrs4PsiDMSHXSVq1x6qROg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 11, 2013 at 1:17 PM, Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> wrote:
> Hi Michael,
>
> I can provide the table schema and the data over which indexing almost
> always fails with tuple not found error.
> Would this be of help. The other issue is that file is 3.2GB so we would
> have work some logistics to transfer this across.
Transferring a data file of a couple of gigs is out of question. My
point was to know if you are able to create a self-contained test case
using automatically generated data of this type:
create table foo as select generate_series(1,100000000) as a, 'bbbb'::text as b;
create index fooi on aa(a);
Or smth like that.
This way you wouldn't need to 1) publish your schema, 2) transfer huge
files of data. And this would make tracking of this error somewhat
easier.
Regards,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2013-12-11 04:26:01 | Re: Trigger Firing Order |
Previous Message | Sandeep Gupta | 2013-12-11 04:17:17 | Re: [Postgres-xc-general] "Tuple not found error" during Index creation |