From: | Keith Parks <emkxp01(at)mtcc(dot)demon(dot)co(dot)uk> |
---|---|
To: | emkxp01(at)mtcc(dot)demon(dot)co(dot)uk, maillist(at)candle(dot)pha(dot)pa(dot)us |
Cc: | hackers(at)postgresql(dot)org, wieck(at)sapserv(dot)debis(dot)de |
Subject: | Re: [HACKERS] crash on new system views |
Date: | 1998-09-15 18:12:39 |
Message-ID: | 199809151812.TAA18523@mtcc.demon.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
>
> > Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
> >
> > >
> > > This query crashes the backend. pg_rules is a new system view:
> > >
> > > BEGIN WORK;
> > > DECLARE c_matches BINARY CURSOR FOR
> > > SELECT count(*)
> > > FROM pg_attrdef t1, pg_rules t2
> > > WHERE t1.adrelid = t2.oid
> > > END WORK;
> > >
> > > Partial backtrace is below. It is crashing in the optimizer.
> >
> > Bruce,
> >
> > I'm getting the same here when testing your query.
> >
> > The odd (maybe not?) thing is that views appear to have
> > a NULL oid for all tuples.
>
> This has always been the case. Views don't have oid.
>
OK, so we shouldn't be able to select a column called oid from
any view?
Keith.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-09-15 18:36:02 | Re: [HACKERS] crash on new system views |
Previous Message | Bruce Momjian | 1998-09-15 15:17:00 | Re: [HACKERS] crash on new system views |