Re: exporting raw parser - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: exporting raw parser
Date
Msg-id 20100527110041.8CCE.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to exporting raw parser  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: exporting raw parser
List pgsql-hackers
Tatsuo Ishii <ishii@postgresql.org> wrote:

> I'm thinking about exporting the raw parser and related modules as a C
> library. Though this will not be an immediate benefit of PostgreSQL
> itself, it will be a huge benefit for any PostgreSQL
> applications/middle ware those need to parse SQL statements.

I read your proposal says "postgres.exe" will link to "libSQL.dll",
and "pgpool.exe" will also link to the DLL, right?

I think it is reasonable, but I'm not sure what part of postgres
should be in the DLL. Obviously we should avoid code duplication
between the DLL and "postgres.exe".

> - create an exportable version of memory manager
> - create an exportable exception handling routines(i.e. elog)

Are there any other issues? For example, - How to split headers for raw parser nodes? - Which module do we define T_xxx
enumerationsand support functions?   (outfuncs, readfuncs, copyfuncs, and equalfuncs)
 

The proposal will be acceptable only when all of the technical issues
are solved. The libSQL should also be available in stand-alone.
It should not be a collection of half-baked functions.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: release notes
Next
From: Robert Haas
Date:
Subject: Re: Stefan's bug (was: max_standby_delay considered harmful)