Re: Bypassing SQL lexer and parser

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Данила Поярков <dev(at)dannote(dot)net>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bypassing SQL lexer and parser
Date: 2015-07-06 17:28:46
Message-ID: CAECtzeU-3ep3fy+g5UhDF47A-zXt47UyyTYaBtEdfViLoJ=s0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Le 6 juil. 2015 7:16 PM, "Данила Поярков" <dev(at)dannote(dot)net> a écrit :
>
> Hello!
>
> What is the best starting point to PostgreSQL internal APIs for operating
directly with the storage (performing basic INSERTs, UPDATEs, SELECTs and
simple JOINs by hand)? I'm looking for something similar to MySQL Cluster
NDB API or InnoDB internal API (the late HailDB and Embedded InnoDB).
>
> Does the PostgreSQL support any other type of plugins/extensions other
than FDW and custom data types? I mean, is it possible to start another
daemon within Postgres without slightly modifying the main codebase?
>

That sounds a lot like a background worker.

> In case you are wondering why could anyone need something like that: I'm
looking for a way to implement a small subset of HTSQL (see [
http://htsql.org/], of course not with the whole HTTP protocol) natively in
one of popular RDBMS without extra URL-to-SQL conversion. Yes, I know that
a lot of hard work was done for making query plans, optimizing etc. but I'm
still really wish to do this for some very specific needs. I'm not going to
completely replace the SQL and thus will be happy to do those manipulations
on a SQL 2008-compliant DBMS.
>

Good luck with that :-)

--
Guillaume

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-07-06 17:56:07 Re: Support for N synchronous standby servers - take 2
Previous Message Jeff Davis 2015-07-06 17:24:52 Re: Parallel Seq Scan