Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Hackers > New relkind (wa...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 5 of 12 Topic 9303 of 11009
Post > Topic >>

New relkind (was Re: Exposing quals)

by david@[EMAIL PROTECTED] (David Fetter) Jul 7, 2008 at 04:26 PM

On Mon, Jul 07, 2008 at 06:46:29PM -0400, Andrew Dunstan wrote:
> >
> > On Mon, 2008-05-05 at 12:01 -0700, David Fetter wrote:
> >
> >> Please find attached the patch, and thanks to Neil Conway and
> >> Korry Douglas for the code, and to Jan Wieck for helping me
> >> hammer out the scheme above.  Mistakes are all mine ;)
> >
> > I see no negative comments to this patch on -hackers.
> >
> > This was discussed here
> > http://wiki.postgresql.org/wiki/PgCon_2008_Developer_Meeting#SQL.2FMED
> > and I had understood the consensus to be that we would go ahead
> > with this?
> >
> > The notes say "Heikki doesn't think this is a long term solution",
> > but in the following discussion it was the *only* way of doing
> > this that will work with non-PostgreSQL databases. So it seems
> > like the way we would want to go, yes?
> >
> > So, can we add this to the CommitFest July page so it can receive
> > some substantial constructive/destructive comments?
> >
> > This could be an im****tant feature in conjunction with Hot
> > Standby.
> 
> The notes say at the end:
> 
> "Jan thinks that showing the node tree will work better. But others
> don't agree with him -- it wouldn't work for PL/perlU. But Jan
> thinks it would work to give it a pointer to the parse tree and the
> range, we'd need to add an access function for the PL."
> 
> For the record, I agree with Jan's suggestion of passing a pointer
> to the parse tree, and offline gave David a suggestion verbally as
> to how this could be handled for PL/PerlU.
> 
> I don't think we should be tied too closely to a string
> representation, although possibly the first and simplest callback
> function would simply stringify the quals.

As I understand Jan's plan, the idea is to create a new relkind with
an exit to user code at leaf nodes in the plan tree.  This would
require an API design for both user C code and for each PL to use, but
would then allow PostgreSQL's optimizer to work on JOINs, etc.

Jan, have I got that right so far?  Do you have something in the way
of a rough patch, docs, etc. for this?

Cheers,
David.
-- 
David Fetter <david@[EMAIL PROTECTED]
> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@[EMAIL PROTECTED]
 to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
 




 12 Posts in Topic:
Exposing quals
david@[EMAIL PROTECTED]   2008-05-05 12:01:18 
Re: Exposing quals
simon@[EMAIL PROTECTED]   2008-07-07 22:33:38 
Re: Exposing quals
heikki@[EMAIL PROTECTED]   2008-07-08 17:51:09 
Re: Exposing quals
andrew@[EMAIL PROTECTED]   2008-07-07 18:46:29 
New relkind (was Re: Exposing quals)
david@[EMAIL PROTECTED]   2008-07-07 16:26:50 
Re: New relkind (was Re: Exposing quals)
simon@[EMAIL PROTECTED]   2008-07-08 07:01:00 
Re: New relkind (was Re: Exposing quals)
postgres@[EMAIL PROTECTED  2008-07-08 15:06:33 
Re: Exposing quals
simon@[EMAIL PROTECTED]   2008-07-08 16:20:06 
Re: Exposing quals
heikki@[EMAIL PROTECTED]   2008-07-08 18:22:23 
Re: Exposing quals
david@[EMAIL PROTECTED]   2008-07-08 08:38:35 
Re: Exposing quals
JanWieck@[EMAIL PROTECTED  2008-07-08 14:41:45 
Re: Exposing quals
david@[EMAIL PROTECTED]   2008-07-14 16:02:28 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Dec 5 8:21:07 CST 2008.