From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Glaesemann <grzm(at)seespotcode(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] possible ecpg vpath build error |
Date: | 2006-09-04 14:49:37 |
Message-ID: | 20060904144937.GA27847@1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, Sep 04, 2006 at 12:06:02AM -0400, Tom Lane wrote:
> Michael Glaesemann <grzm(at)seespotcode(dot)net> writes:
> > There's a lot of duplicate code in ecpg.
>
> No kidding :-(. The parser is bad enough but the datatype library is
> an order of magnitude worse. I don't have a great solution at hand
> though. The backend utils/adt/ code gets to rely on the backend's
Neither have I.
> error handling and memory management protocols, which I surely do
> not propose to remove, but how could we keep common sources when
> ecpglib has to work in a far less friendly environment?
We could modify the backend code to use pgtypeslib, but that would cost
at least a little bit of performance I would guess.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-04 14:57:20 | Re: Planner estimates and cast operations ,... |
Previous Message | Tom Lane | 2006-09-04 14:45:55 | Re: @ versus ~, redux |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Glaesemann | 2006-09-04 14:54:42 | Fix PGPORT reassignment in ecpg regression tests |
Previous Message | Tom Lane | 2006-09-04 14:12:17 | Re: python / 7.4 / FC5 / x86_64 |