Re: [HACKERS] reverse file descriptor to a file name... - Mailing list pgsql-hackers

From The Hermit Hacker
Subject Re: [HACKERS] reverse file descriptor to a file name...
Date
Msg-id Pine.BSF.3.96.980411061211.292B-100000@thelab.hub.org
Whole thread Raw
In response to Re: [HACKERS] reverse file descriptor to a file name...  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] reverse file descriptor to a file name...
List pgsql-hackers
On Fri, 10 Apr 1998, Bruce Momjian wrote:

> >
> >     Oops...I must be using that wrong...I'm getting:
> >
> > NOTICE:  Message from PostgreSQL backend: The Postmaster has informed me
> >      that some other backend died abnormally and possibly corrupted
> >      shared memory.  I have rolled back the current transaction and am
> >      going to terminate your database system connection and exit.
> >      Please reconnect to the database system and repeat your query.
> >
> >
> >     relname is of type NameData ... NameData is a struct, so shouldn't
> > it be:
> >
> >     Relation->rd_rel->relname->data
> >
> >     But, NameData only has one component, data...why make it a struct?
>
> Yep, you are right.  They make is a struct so they can pass it around
> by-value, rather than the normal pointer by-reference for normal arrays.

Odd...rel->rd_rel->relname->data produces:

nbtsearch.c: In function `_bt_moveright':
nbtsearch.c:223: invalid type argument of `->'

But...rel->rd_rel->relname.data works.

    Now, I really really hate pointers to start with...always
have...but can someone confirm which is (should be) right? :(

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] reverse file descriptor to a file name...
Next
From: "Boersenspielteam"
Date:
Subject: Re: [HACKERS] subselect and optimizer