From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | weissig(at)rbg(dot)informatik(dot)tu-darmstadt(dot)de |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: new AM, best way to obtain new block at end of index? |
Date: | 2011-05-07 01:52:48 |
Message-ID: | BANLkTikXyGJ25dHYsVB5q1mP8SL_BZjdSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 28, 2011 at 8:03 AM, Yves Weißig
<weissig(at)rbg(dot)informatik(dot)tu-darmstadt(dot)de> wrote:
> Hi list,
>
> currently I am obtaining a new block at the end of an index with:
>
> buf = ReadBuffer(rel, P_NEW);
>
> but it throws:
>
> ERROR: unexpected data beyond EOF in block 0 of relation base/11874/156053
> HINT: This has been seen to occur with buggy kernels; consider updating
> your system.
>
> system is up to date:
> $ uname -r
> 2.6.35-28-generic
>
> Is there another way to do it? What could be the source of the problem?
Sounds like a bug either in your code, or in the kernel. That's the
right way to do it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-05-07 01:55:38 | Re: SSI non-serializable UPDATE performance |
Previous Message | Robert Haas | 2011-05-07 01:51:39 | Re: (Better) support for cross compiled external modules |