Re: SELECT INTO TABLE busted?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: SELECT INTO TABLE busted?
Date: 1999-02-05 06:13:10
Message-ID: 17315.918195190@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> I am passing the create_view regression test here.

I was afraid you would say that. I'll start digging.

> Have you done a fresh initdb recently?

Yup, this is starting from "distclean" sources and an empty
install directory.

I'm seeing several other regress failures that seem to be caused by
the same SELECT INTO problem. Most are the same "no such table"
failure in a later test session, but the "transactions" test
actually coredumps:

QUERY: BEGIN;
QUERY: SELECT * INTO TABLE xacttest FROM aggtest;
QUERY: INSERT INTO xacttest (a, b) VALUES (777, 777.777);
QUERY: END;
QUERY: SELECT a FROM xacttest WHERE a > 100;
pqReadData() -- backend closed the channel unexpectedly.

I did a little bit of corefile-entrails-examining and found
that heapgettuple was hitting a bad pointer, but ran out of
energy before getting further than that. If that rings any
bells please let me know. I won't have time to look at this
more until Saturday.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 1999-02-05 07:53:53 Re: [HACKERS] small bug fix for ecpg
Previous Message Bruce Momjian 1999-02-05 05:27:22 Re: SELECT INTO TABLE busted?