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

Re: PostGreSQL and recursive queries...

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Tatsuo Ishii" <ishii(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostGreSQL and recursive queries...
Date: 2007-11-30 15:49:34
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> I could imagine problems the planner would have to deal with though, such as
>> what type is "bogon" in this query?
>> WITH RECURSIVE x(bogon) AS (select bogon from x) select * from x;
> Just a note --- that's not the planner's problem, either.  Semantic
> interpretation of the meaning of a query is supposed to be completed
> during parse analysis.

I was being sloppy. I just mean as opposed to the executor. Ie, that the code
to build the plan is harder than actually running it.

  Gregory Stark
  Ask me about EnterpriseDB's RemoteDBA services!

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-11-30 17:15:24
Subject: Re: CommandCounterIncrement versus plan caching
Previous:From: Magnus HaganderDate: 2007-11-30 15:48:11
Subject: Re: .NET or Mono functions in PG

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