Hi Peter and Tom
Following up on our conversation art pgcon.dev
If I understood correctly Peter has some old patch for splitting the
namespaces which could be resurrected to try to move forward on this ?
Can you share what you did there ?
Also, while at it we should extend the function lookup
On Thu, Mar 7, 2024 at 5:46 PM Tom Lane wrote:
>
> Hannu Krosing writes:
> > On Sat, Feb 10, 2024 at 12:38 AM Tom Lane wrote:
> >> Worth noting perhaps that this is actually required by the SQL
> >> standard: per spec, functions and procedures are both "routines"
> >> and share the same
Hannu Krosing writes:
> On Sat, Feb 10, 2024 at 12:38 AM Tom Lane wrote:
>> Worth noting perhaps that this is actually required by the SQL
>> standard: per spec, functions and procedures are both "routines"
>> and share the same namespace,
> Can you point me to a place in the standard where it
Hi Tom
On Sat, Feb 10, 2024 at 12:38 AM Tom Lane wrote:
>
> "David G. Johnston" writes:
> > On Fri, Feb 9, 2024, 12:05 Deepak M wrote:
> >> Folks, When tried to create a function with the same signature as
> >> procedure it fails.
>
> > That seems like a good hint you cannot do it.
"David G. Johnston" writes:
> On Fri, Feb 9, 2024, 12:05 Deepak M wrote:
>> Folks, When tried to create a function with the same signature as
>> procedure it fails.
> That seems like a good hint you cannot do it. Specifically because they
> get defined in the same internal catalog within which
On Fri, Feb 9, 2024, 12:05 Deepak M wrote:
> Hello Hackers,
>
Wrong list, this is for discussions regarding patches.
> Folks, When tried to create a function with the same signature as
> procedure it fails.
>
That seems like a good hint you cannot do it. Specifically because they
get
Hello Hackers,
Folks, When tried to create a function with the same signature as procedure
it fails.
postgres=# create or replace procedure obj1(char) language plpgsql as $$
begin select $1; end; $$;
CREATE PROCEDURE
postgres=# create or replace function obj1(char) returns void language sql
as
