Re: amcheck assert failure
| От | Peter Geoghegan |
|---|---|
| Тема | Re: amcheck assert failure |
| Дата | |
| Msg-id | CAH2-WzncLb59xy4=2gkQnUxHnenCqW1hCTGTX1FwbeH2S5SesQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | amcheck assert failure (Grigory Smolkin <g.smolkin@postgrespro.ru>) |
| Ответы |
Re: amcheck assert failure
|
| Список | pgsql-bugs |
On Fri, Apr 19, 2019 at 6:15 PM Grigory Smolkin
<g.smolkin@postgrespro.ru> wrote:
> Hello, everyone!
> I was running some automated tests with amcheck on PG11 and encountered
> following assertion failure:
>
> TRAP: FailedAssertion("!((( (&(itup)->t_tid)->ip_posid ) & 0xF000) ==
> 0)", File: "nbtutils.c", Line: 2168)
Was the assertion failure on Postgres Pro's fork? I understand that
there are differences in this exact area on the forked version,
because it has to deal with two representations -- the fork had
INCLUDE indexes before the community version, which explicitly
represents the number of attributes in pivot tuples.
I wouldn't usually ask this, but the failure is very basic. It's hard
to believe that it would take this long to notice it.
I also note that you have "fsync = off". I suppose that that might be
relevant, too.
--
Peter Geoghegan
В списке pgsql-bugs по дате отправления: