Re: Any tutorial or FAQ on building an extension? - Mailing list pgsql-hackers

From Matt Culbreth
Subject Re: Any tutorial or FAQ on building an extension?
Date
Msg-id f70c7783-d1e9-4cb5-ba48-c2b2cbe9c1bb@w6g2000yqw.googlegroups.com
Whole thread Raw
In response to Any tutorial or FAQ on building an extension?  (Matt Culbreth <mattculbreth@gmail.com>)
Responses Re: Any tutorial or FAQ on building an extension?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Aug 11, 1:11 pm, j...@agliodbs.com (Josh Berkus) wrote:
> > Is there an easier way of going about this other than replacing the
> > postmaster / postgres components?
>
> I'd start with creating my own extended version to psql (the client
> library), I suppose.  But since I don't really know what kind of
> "transformations" you have in mind, any advice is going to be purely
> speculative.
>

Thanks for the response Josh.

I'm not sure that psql is the right thing for me to do though, since I
want to build a back-end component that takes the place of the
existing postmaster.  Very possible I misunderstood you though.

To clarify, essentially what I want to do is this:

Client [ psql | JDBC driver | pgAdmin | etc. ] issues a Query
[ "Select * from sales" ]   |   |   \/
My new component intercepts this, and decides if it wants to do
something   |   |   \/
If it does not, it simply passes this on to the real PostgreSQL server
running somewhere   |   |   \/
If it does, it passes the request over to my new server (via sockets),
does its work, and pass back the results   |   |   \/
The client gets the results back, either from PostgreSQL or from my
new server, and goes about its way.




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)
Next
From: Mark Mielke
Date:
Subject: Re: "Hot standby"?