Re: Using postgres planner as standalone component

From: Álvaro Hernández Tortosa <aht(at)8kdata(dot)com>
To: Ricky Stevens <ristevenj(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Using postgres planner as standalone component
Date: 2017-07-02 21:21:16
Message-ID: fa90766e-1091-3719-4ab1-383ce81ed4d3@8kdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/07/17 22:48, Ricky Stevens wrote:
> Hi,
>
> For one of my personal projects I am interested in using the
> PostgreSQL planner as a standalone library. However, I would like to
> run this as an embedded library instead of actually creating anything
> on disk.
>
> I've realized that postgres has several pg_operator, pg_class etc.
> tables which it uses for query planning purposes. Is there any
> PostgreSQL component interface whose implementation could be
> overridden to not actually try to read these tables from disk but
> instead read it from a custom memory region that is managed by my code.
>
> Thanks!
>

Maybe you'd like to consider gporca
https://github.com/greenplum-db/gporca as an alternative. You may also
want to look at Calcite https://calcite.apache.org/docs/ if you were
more into the Java world.

Álvaro

--

Álvaro Hernández Tortosa

-----------
<8K>data

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-07-02 22:02:24 Re: Race-like failure in recovery/t/009_twophase.pl
Previous Message Tom Lane 2017-07-02 21:10:31 Re: Race-like failure in recovery/t/009_twophase.pl