Re: [Npgsql-general] Get function OID and function calling support

Started by Dave Pageabout 23 years ago5 messages
#1Dave Page
dpage@vale-housing.co.uk

-----Original Message-----
From: Kristis Makris [mailto:devcore@freeuk.com]
Sent: 07 January 2003 03:05
To: Francisco Figueiredo Jr.
Cc: npgsql-general@gborg.postgresql.org
Subject: Re: [Npgsql-general] Get function OID and function
calling support

Hi Francicso,

I could, however, call a function using the command "select

f1()" and

"select * from f1()", for example but as a normal query instead of
funcion call.

That's how I've seen function call examples for a long time
now. I'm not sure what the intent was with having the
FunctionCall message in the Postgres protocol v2...

I wonder if Dave knows anything about this, or maybe the
pgsql-odbc mailing list guys.

Sorry, don't know. Can anyone on pgsql-hackers tell us the purpose of
the FunctionCall message?

Regards, Dave.

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Dave Page (#1)

"Dave Page" <dpage@vale-housing.co.uk> writes:

Sorry, don't know. Can anyone on pgsql-hackers tell us the purpose of
the FunctionCall message?

It's used to invoke the "fast path" function call code
(src/backend/tcop/fastpath.c). libpq's large-object routines use this,
but little else does AFAIK. The current protocol is sufficiently broken
(see comments in fastpath.c) that I'd not really encourage people to use
it until we can fix it --- hopefully that will happen in 7.4.

regards, tom lane

PS: what in the world is npgsql-general@gborg.postgresql.org ... is that
a real mailing list, and if so why? It sounds a bit, um, duplicative.

#3Dave Page
dpage@vale-housing.co.uk
In reply to: Tom Lane (#2)

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: 07 January 2003 15:01
To: Dave Page
Cc: Kristis Makris; Francisco Figueiredo Jr.;
npgsql-general@gborg.postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [Npgsql-general] Get function OID and
function calling support

"Dave Page" <dpage@vale-housing.co.uk> writes:

Sorry, don't know. Can anyone on pgsql-hackers tell us the

purpose of

the FunctionCall message?

It's used to invoke the "fast path" function call code
(src/backend/tcop/fastpath.c). libpq's large-object routines
use this, but little else does AFAIK. The current protocol
is sufficiently broken (see comments in fastpath.c) that I'd
not really encourage people to use it until we can fix it ---
hopefully that will happen in 7.4.

OK, Thanks.

PS: what in the world is npgsql-general@gborg.postgresql.org
... is that a real mailing list, and if so why? It sounds a
bit, um, duplicative.

npgsql-general@gborg.postgresql.org is the general discussion list for
the Npgsql project on Gborg. It's a .NET data provider for PostgreSQL
that works with .NET programs written in MS VC++, C# or VB.NET not to
mention Mono.

Not to be confused with pgsql-general :-)

Regards, Dave.

#4Greg Copeland
greg@CopelandConsulting.Net
In reply to: Tom Lane (#2)
Re: [Npgsql-general] Get function OID and function

San someone point me to what exactly is planned for the
protocol/networking stuff? Networking/protocols is one of my fortes and
I believe that I could actually help here.

Regards,

Greg

On Tue, 2003-01-07 at 09:01, Tom Lane wrote:

"Dave Page" <dpage@vale-housing.co.uk> writes:

Sorry, don't know. Can anyone on pgsql-hackers tell us the purpose of
the FunctionCall message?

It's used to invoke the "fast path" function call code
(src/backend/tcop/fastpath.c). libpq's large-object routines use this,
but little else does AFAIK. The current protocol is sufficiently broken
(see comments in fastpath.c) that I'd not really encourage people to use
it until we can fix it --- hopefully that will happen in 7.4.

regards, tom lane

PS: what in the world is npgsql-general@gborg.postgresql.org ... is that
a real mailing list, and if so why? It sounds a bit, um, duplicative.

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

--
Greg Copeland <greg@copelandconsulting.net>
Copeland Computer Consulting

#5Francisco Figueiredo Jr.
fxjrlists@yahoo.com.br
In reply to: Tom Lane (#2)
--- Tom Lane <tgl@sss.pgh.pa.us> escreveu: 

"Dave Page" <dpage@vale-housing.co.uk> writes:

Sorry, don't know. Can anyone on pgsql-hackers tell us the purpose of
the FunctionCall message?

It's used to invoke the "fast path" function call code
(src/backend/tcop/fastpath.c). libpq's large-object routines use this,
but little else does AFAIK. The current protocol is sufficiently broken
(see comments in fastpath.c) that I'd not really encourage people to use
it until we can fix it --- hopefully that will happen in 7.4.

Ok, as Kristis already said about how functions are being commonly called, I
will implement it this way: transforming the function call into a "select
<function_name>" statement. I already have some working code and I will clean
it and commit it soon.

Thanks all!

=====
Regards,
Francisco Figueiredo Jr.

_______________________________________________________________________
Busca Yahoo!
O melhor lugar para encontrar tudo o que voc� procura na Internet
http://br.busca.yahoo.com/