Skip site navigation (1) Skip section navigation (2)

Re: exporting raw parser

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp
Cc: ishii(at)sraoss(dot)co(dot)jp, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: exporting raw parser
Date: 2010-05-27 03:01:56
Message-ID: 20100527.120156.55840891.t-ishii@sraoss.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
> My "stand-alone" means libSQL can be used from many modules
> without duplicated codes. For example, copy routines for raw
> parse trees should be in the DLL rather than in postgres.exe.
> 
> Then, we need to consider other products than pgpool. Who will
> use the dll? If pgpool is the only user, we might not allow to
> modify core codes only for one usecase. More research other than
> pgpool is required to decide the interface routines for libSQL.

If the user of the new API is only pgpool-II, I hadn't made the
propose in the first place. It's a waste of time and I would rather
keep on borrowing the parse code. I thought there were several people
who needed the API as well in the cluster meeting. If somebody who
made such a vote in the meeting is on the list, please express your
opinion for the API.

I'm not in the position of speaking for other products.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

In response to

pgsql-hackers by date

Next:From: Tatsuo IshiiDate: 2010-05-27 03:07:58
Subject: pg_trgm
Previous:From: KaiGai KoheiDate: 2010-05-27 03:00:56
Subject: Re: ExecutorCheckPerms() hook

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group