Martin Pihlak writes:
> Attached documentation patch attempts to clarify this.
Applied in a slightly modified form.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/ma
2009/2/22 Martin Pihlak :
> Pavel Stehule wrote:
>> then documentation is probably little bit wrong (needs some additional
>> comment) . This text specifies using option 'all' for sql functions.
>>
>
> Attached documentation patch attempts to clarify this.
>
> regards,
> Martin
>
>
thank you
Pavel
Pavel Stehule wrote:
> then documentation is probably little bit wrong (needs some additional
> comment) . This text specifies using option 'all' for sql functions.
>
Attached documentation patch attempts to clarify this.
regards,
Martin
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/conf
2009/2/22 Tom Lane :
> Pavel Stehule writes:
>> postgres=# create or replace function test1(i integer) returns int as
>> $$ select $1; $$ language sql;
>
> This function will get inlined, so there's no separate entity to track
> the execution of.
>
then documentation is probably little bit wrong
Pavel Stehule writes:
> postgres=# create or replace function test1(i integer) returns int as
> $$ select $1; $$ language sql;
This function will get inlined, so there's no separate entity to track
the execution of.
regards, tom lane
--
Sent via pgsql-hackers mailing li
Hello
I am checking this functionality and I am afraid, so option all is broken.
postgres=# select * from pg_stat_user_functions; funcid | schemaname
| funcname | calls | total_time | self_time
++--+---++---
24608 | public | test |
