Re: [SQL] Postgres backend crash on alpha

From: Mark Volpe <volpe(dot)mark(at)epamail(dot)epa(dot)gov>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-sql(at)postgreSQL(dot)org
Subject: Re: [SQL] Postgres backend crash on alpha
Date: 2000-02-16 18:16:49
Message-ID: 38AAE991.791D8E2@epamail.epa.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Yup, it's fixed.

Bruce Momjian wrote:
>
> I would like you to try this on the current snapshot on our ftp server.
> I suspect it has been fixed, but if not, we would like to get it fixed
> because we are starting beta in a few days.
>
> > The following sequence causes the backend
> > to crash:
> >
> > CREATE TABLE test1 (a text);
> > CREATE TABLE test2 (b text);
> >
> > CREATE RULE test_insert AS ON INSERT TO test1
> > DO INSTEAD INSERT INTO test2 VALUES (NEW.a);
> >
> > INSERT INTO test1 VALUES ('crash');
> >
> >
> > For some reason this only occurs on the alpha platform
> > (tried on alpha and linux).
> >
> > If I try this using ints it works fine, though. And the use
> > of "NEW" seems to be what's screwing it up.
> >
> > Is there a fix for this?
> > It is crashing in the _copyConst function on this line:
> >
> > length = VARSIZE(from->constvalue)
> >
> > Thanks,
> > Mark
> >
> > ************
> >
> >
>
> --
> Bruce Momjian | http://www.op.net/~candle
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ************

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Mark Volpe 2000-02-16 22:14:03 Multiple rule actions
Previous Message Bruce Momjian 2000-02-16 16:58:07 Re: [SQL] Postgres backend crash on alpha