From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Re: [QUESTIONS] is Postgres an SQL-based database? |
Date: | 1998-02-05 01:52:08 |
Message-ID: | 34D91B48.61992D5A@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I have gram.y patches to do this. No visible effect on the regression execution speed,
> > which thanks to Bruce is on my machine down to a record 2:23 elapsed execution time;
> > the last speeds were in the 2:31 range.
> >
> > I'm planning on bumping the gram.y cvs version to 2.0 for this change, due to the
> > _large_ number of accumulated improvements. Any objections?
>
> Go ahead. Are there security problems?
Security problems with the patch? No, I don't think so. The only thing I'm doing is
implementing xlateSqlFunc() similarly to the existing xlateSqlType(), and defining a
"func_name" state in place of just "name" which was used before.
The only downside is that backend functions implemented with names "char_length" and
"character_length" will be masked by the parser translation so cannot be executed. In this
case I think that is OK, but I should put something in the new docs about that :)
- Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-02-05 02:01:59 | Re: new yacc problem |
Previous Message | Vadim B. Mikheev | 1998-02-05 01:51:25 | Re: [HACKERS] Execution time. |