Re: Bypassing SQL lexer and parser - Mailing list pgsql-hackers

From Guillaume Lelarge
Subject Re: Bypassing SQL lexer and parser
Date
Msg-id CAECtzeU-3ep3fy+g5UhDF47A-zXt47UyyTYaBtEdfViLoJ=s0g@mail.gmail.com
Whole thread Raw
In response to Bypassing SQL lexer and parser  (Данила Поярков <dev@dannote.net>)
Responses Re: Bypassing SQL lexer and parser
List pgsql-hackers
<p dir="ltr">Le 6 juil. 2015 7:16 PM, "Данила Поярков" <<a href="mailto:dev@dannote.net">dev@dannote.net</a>> a
écrit :<br/> ><br /> > Hello!<br /> ><br /> > What is the best starting point to PostgreSQL internal APIs
foroperating directly with the storage (performing basic INSERTs, UPDATEs, SELECTs and simple JOINs by hand)? I'm
lookingfor something similar to MySQL Cluster NDB API or InnoDB internal API (the late HailDB and Embedded InnoDB).<br
/>><br /> > 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?<br
/>><p dir="ltr">That sounds a lot like a background worker.<p dir="ltr">> In case you are wondering why could
anyoneneed something like that: I'm looking for a way to implement a small subset of HTSQL (see [<a
href="http://htsql.org/">http://htsql.org/</a>],of course not with the whole HTTP protocol) natively in one of popular
RDBMSwithout extra URL-to-SQL conversion. Yes, I know that a lot of hard work was done for making query plans,
optimizingetc. but I'm still really wish to do this for some very specific needs. I'm not going to completely replace
theSQL and thus will be happy to do those manipulations on a SQL 2008-compliant DBMS.<br /> ><p dir="ltr">Good luck
withthat :-) <br /><p dir="ltr">-- <br /> Guillaume 

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Parallel Seq Scan
Next
From: Josh Berkus
Date:
Subject: Re: Support for N synchronous standby servers - take 2