Re: [HACKERS] Exposing quals

2008-07-14 Thread David Fetter
On Tue, Jul 08, 2008 at 02:41:45PM -0400, Jan Wieck wrote: > Here, > > I talked to my supervisor here in Toronto (that's where I am this week) > and Afilias actually sees enough value in this for me to go and spend > time officially on it. Yay! > The ideas I have so far are as follows: > > Do

Re: [HACKERS] Exposing quals

2008-07-08 Thread Jan Wieck
On 7/8/2008 11:38 AM, David Fetter wrote: On Tue, Jul 08, 2008 at 06:22:23PM +0300, Heikki Linnakangas wrote: Simon Riggs wrote: SQL, in text form, is the interface to other databases. You can't pass half a plan tree to Oracle, especially not a PostgreSQL plan tree. It has to be text if you wis

Re: [HACKERS] Exposing quals

2008-07-08 Thread David Fetter
On Tue, Jul 08, 2008 at 06:22:23PM +0300, Heikki Linnakangas wrote: > Simon Riggs wrote: >> SQL, in text form, is the interface to other databases. You can't >> pass half a plan tree to Oracle, especially not a PostgreSQL plan >> tree. It has to be text if you wish to send a query to another >> RDB

Re: [HACKERS] Exposing quals

2008-07-08 Thread Heikki Linnakangas
Simon Riggs wrote: SQL, in text form, is the interface to other databases. You can't pass half a plan tree to Oracle, especially not a PostgreSQL plan tree. It has to be text if you wish to send a query to another RDBMS, or another version of PostgreSQL. Oh, I see. Agreed. Though note that the

Re: [HACKERS] Exposing quals

2008-07-08 Thread Simon Riggs
On Tue, 2008-07-08 at 17:51 +0300, Heikki Linnakangas wrote: > Simon Riggs wrote: > > 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 wa

Re: [HACKERS] Exposing quals

2008-07-08 Thread Heikki Linnakangas
Simon Riggs wrote: 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? How did you come to the conclusion that this

Re: New relkind (was Re: [HACKERS] Exposing quals)

2008-07-08 Thread Hans-Juergen Schoenig
Simon Riggs wrote: On Mon, 2008-07-07 at 16:26 -0700, David Fetter wrote: On Mon, Jul 07, 2008 at 06:46:29PM -0400, Andrew Dunstan wrote: 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 cou

Re: New relkind (was Re: [HACKERS] Exposing quals)

2008-07-07 Thread Simon Riggs
On Mon, 2008-07-07 at 16:26 -0700, David Fetter wrote: > On Mon, Jul 07, 2008 at 06:46:29PM -0400, Andrew Dunstan wrote: > > > > > 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 hand

New relkind (was Re: [HACKERS] Exposing quals)

2008-07-07 Thread David Fetter
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. M

Re: [HACKERS] Exposing quals

2008-07-07 Thread andrew
> > 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 -hac

Re: [HACKERS] Exposing quals

2008-07-07 Thread Simon Riggs
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. Thi

[HACKERS] Exposing quals

2008-05-05 Thread David Fetter
Folks, I'd like to make it possible to see qualifiers from inside functions in PostgreSQL. For my particular case, and for dblink, it would allow user-space code to some remove bottlenecks which make currently make inter-DBMS communication extremely inefficient. The current code returns one (pot