On Tue, Dec 10, 2013 at 11:23 PM, Michael Paquier wrote:
> On Wed, Dec 11, 2013 at 1:17 PM, Sandeep Gupta
> 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 is
In 1.0, we added new APIs to GTM so that vacuum can run with global
XID and snapshot. We may need more improvement to use this.
It is wonderful if Mason provides a patch to fix this.
Regards;
---
Koichi Suzuki
2013/12/11 Michael Paquier :
> On Tue, Dec 10, 2013 at 11:00 PM, Mason Sharp wrote
We made changes in internal snapshot handling to solve another problem around
last December to January. It will be very helpful if you try commits before
and after this period. This period’s change could be most suspect.
Best;
---
Koichi Suzuki
2013/12/12 9:19、Sandeep Gupta
mailto:gupta.san
Hi Mason,
Thank you so much for taking the time. We are using pgxc 1.1. This was the
stable release. Let me give it a try with commits from previous versions.
May take some time. I will get back to you with an update.
-Sandeep
On Wed, Dec 11, 2013 at 8:55 AM, Mason Sharp wrote:
>
>
>
> On T
On Wed, Dec 11, 2013 at 1:17 PM, Sandeep Gupta 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 tran
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.
Let me know.
-Sandeep
On Mon, Dec 9, 2013 a
On Tue, Dec 10, 2013 at 11:00 PM, Mason Sharp wrote:
> In our StormDB fork (now TransLattice Storm) I made some changes to address
> some issues that were uncovered with XC. I am not sure if it will address
> this specific issue above, but in most cases we make it an error instead of
> falling bac
On Mon, Dec 9, 2013 at 8:49 PM, Michael Paquier
wrote:
> On Tue, Dec 10, 2013 at 7:17 AM, Sandeep Gupta
> wrote:
> > We are trying to trace cause and potential solution of "tuple not found"
> > error with postgres-xc. The problem happens when indexing a large file.
> It
> > seems the autovaccum
On Tue, Dec 10, 2013 at 7:17 AM, Sandeep Gupta wrote:
> We are trying to trace cause and potential solution of "tuple not found"
> error with postgres-xc. The problem happens when indexing a large file. It
> seems the autovaccum locks certain cache pages that the indexer tries to
> read. The inde
Hello All,
We are trying to trace cause and potential solution of "tuple not found"
error with postgres-xc. The problem happens when indexing a large file. It
seems the autovaccum locks certain cache pages that the indexer tries to
read. The indexing fails with "tuple not found" error.
I am sur
Agreed. However, the "tuple not found" error problem seems to happen with
postgres as well, if not in the particular case index creation over large
datasets. It would helpful to know in that scenario what are the fixes and
how to avoid it in the first place.
The solution/fixes for postgres will ca
On 12/9/2013 10:07 AM, RUSHI KAW wrote:
I have been running Postgresxc 1.1
you'd probably be best off finding the postgresql-xc list, as that is
really a rather different system, even if it is forked from community
postgresql.
--
john r pierce 37N 122W
Hi All,
I have been running Postgresxc 1.1 on a 40 core, 1 TB RAM, Intel(R) Xeon(R)
machine.
The data tables size with which the database is populated is approx 14GB.
The issue is that during the index creation time on the big table of approx
13GB size, the following error occurs:
ERROR: could
13 matches
Mail list logo
