RE: [HACKERS] Sure enough, SI buffer overrun is broken

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: <prlw1(at)cam(dot)ac(dot)uk>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] Sure enough, SI buffer overrun is broken
Date: 2000-01-27 16:30:54
Message-ID: NDBBIJLOILGIKBGDINDFOEGKCCAA.Inoue@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Patrick Welche [mailto:prlw1(at)newn(dot)cam(dot)ac(dot)uk]
> > > I built the current sources with MAXNUMMESSAGES set to 32 in
> > > src/include/storage/sinvaladt.h. The regular regress tests
> > > run OK, with just a few NOTICEs about 'cache state reset'
> > > and 'SI buffer overflow' inserted in the normal outputs
> > > (as you'd expect, if SI overrun occurs).
> > >
> > > However, the parallel tests crash spectacularly, with weird errors
> > > and Assert() coredumps. Some of the unexpected messages in the
> > > postmaster log are:
> > >
> >
> > Certainly crash occurs.
> > But I couldn't see such Assert messages.
> >
> > OK,I will examine tomorrow.
>
> How's it going? Can I help ?
>

Of cource you can help us.
As Tom wrote
1) set MAXNUMMESSAGES of src/include/storage/sinvaldt.h to 32
2) cd src/test/regress
3) make all runcheck

You would see crash and various kind of unexpected messages.
My another posting may be a little help.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-01-27 16:30:57 RE: [GENERAL] Problem with SELECT on large negative INT4
Previous Message Don Baccus 2000-01-27 16:23:32 Re: [HACKERS] Ars Digita and PostgreSQL