On 4/27/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Is the source easier to maintain?
Yes, aside from extra lookahead, that was my main motivation.
--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324
---(end of broadcast)---
Jonah H. Harris wrote:
> On 4/27/06, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > Is it faster? How much faster?
>
> I'm not sure, I haven't done direct timings on it vs. the bison
> version. When I wrote it, I wasn't really concerned with the time it
> took to parse.
Is the source ea
On 4/27/06, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Is it faster? How much faster?
I'm not sure, I haven't done direct timings on it vs. the bison
version. When I wrote it, I wasn't really concerned with the time it
took to parse.
--
Jonah H. Harris, Database Internals Architect
En
For the sake of saying again, I already have a recursive-descent
parser for PostgreSQL written in a PCCTS grammar. It's something I
started writing years ago, but I'd be willing to consider open
sourcing it if the PostgreSQL community will really entertain the
thought of switching.
Unfortunately
On 4/27/06, Tom Lane <[EMAIL PROTECTED]> wrote:
> ... and is far more maintainable than an RD parser, and is not a
> performance bottleneck. I've never seen yyparse occupy as much as 2%
> of a backend profile ...
Not more maintainable by any stretch of the imagination. For example,
try and remov
On 4/27/06, Stephen Frost <[EMAIL PROTECTED]> wrote:
> The answer to that can certainly be "performance" provided other factors
> (such as maintainability) don't change much. If you could show that
> then I think such a switch would be very seriously considered.
IMHO, switching parser-types (and
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> Unfortunately, this discussion usually ends up with, "why would we
> want to change what we have now when it already works?"
... and is far more maintainable than an RD parser, and is not a
performance bottleneck. I've never seen yyparse occupy as m
* Jonah H. Harris ([EMAIL PROTECTED]) wrote:
> Unfortunately, this discussion usually ends up with, "why would we
> want to change what we have now when it already works?"
The answer to that can certainly be "performance" provided other factors
(such as maintainability) don't change much. If you
On 4/27/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> We talked about it when GCC announced their switch. The conclusion was
> that our grammar is still too much a moving target, so it would be too
> difficult to mantain such a grammar.
For the sake of saying again, I already have a recursive-d
Jesper Pedersen wrote:
> I have been thinking about this for a while and now that Google Summer of Code
> is coming I thought I would share this idea.
>
> The GCC people have traded their bison/flex parser with a hand written
> recursive-descent parser for a nice speed up.
>
> So it would be int
On Tue, Apr 25, 2006 at 10:30:26PM +0200, Jesper Pedersen wrote:
> Hi.
>
> I have been thinking about this for a while and now that Google Summer of Code
> is coming I thought I would share this idea.
>
> The GCC people have traded their bison/flex parser with a hand written
> recursive-descent p
Hi.
I have been thinking about this for a while and now that Google Summer of Code
is coming I thought I would share this idea.
The GCC people have traded their bison/flex parser with a hand written
recursive-descent parser for a nice speed up.
So it would be interesting to see if PostgreSQL wou
Josh Berkus wrote:
Jonah,
Where do we stand on this?
Google sent me the docs on this year's SoC literally 2 hours ago. I need
to read through them and start trying to connect mentors and students and
projects.
Do you think a proposal to work on a TPC-App (Java) and TPC-E (next
generat
Jonah,
> Where do we stand on this?
Google sent me the docs on this year's SoC literally 2 hours ago. I need
to read through them and start trying to connect mentors and students and
projects.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
---(end of broadcast
Where do we stand on this?
--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Sat, 2006-04-08 at 12:54 -0700, Josh Berkus wrote:
> As well as projects and students, we also will need mentors for Summer of
> Code
> projects. I'm not sure exactly what time commitment being a mentor involves,
> but I imagine that it's at least a couple dozen hours over the summer.
> V
Folks,
As well as projects and students, we also will need mentors for Summer of Code
projects. I'm not sure exactly what time commitment being a mentor involves,
but I imagine that it's at least a couple dozen hours over the summer.
Volunteers, please contact me. Note that we can have corpo
On Thu, Apr 06, 2006 at 06:31:01AM -0500, Jim C. Nasby wrote:
> On Wed, Apr 05, 2006 at 11:55:15PM -0300, Marc G. Fournier wrote:
> > On Wed, 5 Apr 2006, Jim Nasby wrote:
> >
> > >One idea that comes to mind is to come up with a list of popular OSS
> > >projects that we'd like to see add PostgreS
On Wed, Apr 05, 2006 at 11:55:15PM -0300, Marc G. Fournier wrote:
> On Wed, 5 Apr 2006, Jim Nasby wrote:
>
> >One idea that comes to mind is to come up with a list of popular OSS
> >projects that we'd like to see add PostgreSQL support and have students
> >work on those...
>
> As nice an idea a
"Josh Berkus" wrote
>
> Sure, although the important part is to find students. I'm not sure how
we
> do that.
>
I noticed two email domains are @mit.edu and @cs.toronto.edu but I am afraid
both of them are not students any more :-)
Regards,
Qingqing
---(end of broadc
On Wed, 5 Apr 2006, Jim Nasby wrote:
One idea that comes to mind is to come up with a list of popular OSS projects
that we'd like to see add PostgreSQL support and have students work on
those...
As nice an idea as this is, we'd also need to quickly co-ordinate with
those projects to make sur
From the main website, hit developers, roadmap and then the TODO
link on that page.
On Apr 5, 2006, at 1:44 PM, Nathan Buchanan wrote:
A list of simpler TODOs would be great. I might be interested in
doing something (probably w/o the summer of code because I have a
summer job). We'll see a
One idea that comes to mind is to come up with a list of popular OSS
projects that we'd like to see add PostgreSQL support and have
students work on those...
As for finding students, I believe a call on -general and -announce
would probably produce results. I know there's some professors on
On Apr 5, 2006, at 5:04 PM, Marc G. Fournier wrote:
Sure, although the important part is to find students. I'm not
sure how we
do that.
Do we have any professors online?
I'm not one, but I know some. If there is a link with details and
perhaps a list of possible projects, I'll be happ
On Wed, 5 Apr 2006, Josh Berkus wrote:
Robert,
Summer of Code projects dont have to revolve around the core project...
for example drupal got like 11 projects last year and bricolage got a
few too; I got a small list of items that could be looked at that are
sort of 3rd party projects, should
Robert,
> Summer of Code projects dont have to revolve around the core project...
> for example drupal got like 11 projects last year and bricolage got a
> few too; I got a small list of items that could be looked at that are
> sort of 3rd party projects, should we attempt to collaborate on puttin
Summer of Code projects dont have to revolve around the core project... for
example drupal got like 11 projects last year and bricolage got a few too; I
got a small list of items that could be looked at that are sort of 3rd party
projects, should we attempt to collaborate on putting up a list so
A list of simpler TODOs would be great. I might be interested in doing
something (probably w/o the summer of code because I have a summer
job). We'll see after exams finish.
Please post something about where we can find this TODO list when it is available.
Thanks,
NathanOn 4/5/06, Jim Nasby <[EMA
If nothing else, any of the 'beginner todo' items are likely
candidates, though I suspect none of them individually are enough
work for an entire summer.
If no one beats me to it, I'll try and compile a list of likely TODOs
for this.
On Apr 5, 2006, at 12:16 AM, Josh Berkus wrote:
Folks
Folks,
I've been warned that Summer of Code is coming up again soon. We need to be
ready with proposals which are officially endorsed by the PostgreSQL project.
Which means we need:
a) Projects which could be accomplished in a summer, and
b) Students to do them.
We have one or two weeks to g
30 matches
Mail list logo
