From: | Ron Peterson <rpeterson(at)yellowbank(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | SPI & file locations |
Date: | 2000-05-26 15:24:41 |
Message-ID: | 392E9739.2314098C@yellowbank.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I'm afraid this might sound rather dumb. I'm hoping I can just get a
little clarification about file locations.
I've just started playing w/ SPI. As a first stab, I thought I'd
compile a couple of the test applications in /contrib.
I pointed gcc to include files from /usr/local/pgsql - i.e. 'gcc ...
-I/usr/local/pgsql/include ...'. This of course didn't work.
/usr/local/pgsql/include/executor/spi.h attempts to include files which
don't exist in the install directory. They only exist in
/usr/local/src/postgresql-7.0/src/include (or wherever you put the
source).
After installation, shouldn't everything you need be in
/usr/local/pgsql?
It's simple enough to just use
/usr/local/src/postgresql-7.0/src/include. But I don't know when to use
one, and when to use the other.
Sorry if this is a completely naive question. I'm pretty much flying
solo here. I'm an architect who's gotten frustrated with the
scaleability limitations of using something like MS Access. I'm the
only person I know who uses any *NIX whatsoever, nevermind PostgreSQL.
C/C++ doesn't bother me, but I'm really not too familiar w/ *NIX file
conventions, etc.
-Ron-
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Barnes | 2000-05-26 15:43:25 | RE: PG 7.0 is 2.5 times slower running a big report |
Previous Message | Bruce Momjian | 2000-05-26 15:22:00 | Re: createdb -- alternate locations |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-26 15:37:39 | \h SELECT |
Previous Message | Tom Lane | 2000-05-26 15:13:16 | Re: Postgresql 7.0 JDBC exceptions - broken connections ? |