Re: Configuring Postgres to Add A New Source File

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tareq Aljabban <tareq(dot)aljabban(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Configuring Postgres to Add A New Source File
Date: 2012-01-30 15:07:16
Message-ID: CA+TgmoZkK=HhnotWm-8LdC3OmfzCWSY5d=QaPGV3d+EO9XhG5g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 27, 2012 at 6:37 PM, Tareq Aljabban
<tareq(dot)aljabban(at)gmail(dot)com> wrote:
> Indeed, I'm a beginner in "Make", but I read few tutorials and was able to
> do what I wanted outside of PG using a simple make file.
> Now, when moving to PG, I found the Make structure much more complicated and
> didn't know where to add my configuration.
> I'm looking only for this file to run in PG (the required functionality is
> done already). My code will be a part of the backend, so I want to keep it
> there.

Uh, no it won't. The compile command you showed had it creating a
standalone executable, hdfs_test.

You're likely to find that linking a JVM into the backend
significantly decreases the overall robustness of the system. For
example, ^C isn't going to be able to abort out of processing a query
that's off doing something inside the JVM.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-01-30 15:18:32 Re: Group commit, revised
Previous Message Robert Haas 2012-01-30 15:03:09 Re: Multithread Query Planner