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

Re: ECPG failed and Postmaster getting bigger in using perl Pg

From: SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: ECPG failed and Postmaster getting bigger in using perl Pg
Date: 2000-05-10 10:53:28
Message-ID: 39193FA830C.6548SAKAIDA@smtp.psn.ne.jp (view raw or flat)
Thread:
Lists: pgsql-interfaces
Michael Meskes <meskes(at)postgresql(dot)org> wrote:

> >   This is a bug of pre-processor in PostgreSQL-7.0RC5.
> 
> ARGH!
> 
> >   The solutions of the bug:
> > 
> >  1. Don't use a struct host variable.
> 
> Not really a solution.

  This solution would be effective only when ecpg is not fixed ;-).


> >  2. Apply the next patch.
> > 
> > *** postgresql-7.0RC5/src/interfaces/ecpg/preproc/type.c.orig	Wed May 10 14:45:55 2000
> > --- postgresql-7.0RC5/src/interfaces/ecpg/preproc/type.c	Wed May 10 14:46:43 2000
> > ***************
> > *** 198,203 ****
> > --- 198,209 ----
> >   void
> >   ECPGdump_a_type(FILE *o, const char *name, struct ECPGtype * typ, const char *ind_name, struct ECPGtype * ind_typ, const char *prefix, const char *ind_prefix)
> >   {
> > + 	if (ind_typ == NULL)
> > + 	{
> > + 		ind_typ = &ecpg_no_indicator;
> > + 		ind_name = "no_indicator";
> > + 	}
> > + 
> 
> This has been in before. I have no idea where it got lost. 

  Probably, when you were editting it, you have made a mistake,
I think :-). 


  BTW If ecpg is fixed, we can use a struct indicator, too. (ex. 
select * into :temp :ind_temp from foo_1 ..)  It is wonderful that 
such a struct host variable can be used.  Ecpg is very good tool.

--
Regards,
SAKAIDA Masaaki  -- Osaka, Japan



In response to

Responses

pgsql-interfaces by date

Next:From: Dave PageDate: 2000-05-10 11:22:23
Subject: ODBC & v7.0(Rel) Errors with Users and Databases
Previous:From: Michael HolopainenDate: 2000-05-10 07:49:03
Subject: Lotus Approach problems, please help meeeeee! ;)

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