| From: | Sandeep Gupta <gupta(dot)sandeep(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: "Tuple not found error" during Index creation |
| Date: | 2013-12-09 18:43:52 |
| Message-ID: | CAAywg7vy3cdPFezJPZUcYf-Xp90iEv1fN5ENOnwj-79a0NfZ-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 carry over to pgxc because the low
level stuff (blocks, files, indexes) etc. postgres-xc is really the same as
in postgres.
-Sandeep
On Mon, Dec 9, 2013 at 1:23 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> 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
> somewhere on the middle of the left coast
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Willy-Bas Loos | 2013-12-09 20:44:44 | Re: client that supports editing views |
| Previous Message | John R Pierce | 2013-12-09 18:23:59 | Re: "Tuple not found error" during Index creation |