Re: [GENERAL] Persistent variables between cross-calls in C functions - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: [GENERAL] Persistent variables between cross-calls in C functions
Date
Msg-id 20030325094939.W41500-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Persistent variables between cross-calls in C functions  ("Fabio Furia Silva" <ff-@uol.com.br>)
List pgsql-hackers
On Tue, 25 Mar 2003, Fabio Furia Silva wrote:

> For example, the following function doesn't work as expected:
>
> /********************************/
>     #include "postgres.h"
>     #include "fmgr.h"
>
>     PG_FUNCTION_INFO_V1(next_value);
>
>     Datum next_value(PG_FUNCTION_ARGS)
>     {
>     static int n;
>     PG_RETURN_INT32(n);
>     n++;
>     }
>
> /********************************/
>     create function next_value()
>     returns integer as
>     'next.so' language C;
>
> /********************************/
> Calling
>
>     select next_value();
>
> will always return 0,
> even if I declare 'n' as a global variable outside the C function.

Which seems right since the n++ is never executed (being after the return
statement).  Does it do what you want if you increment first?


pgsql-hackers by date:

Previous
From: "Fabio Furia Silva"
Date:
Subject: Persistent variables between cross-calls in C functions
Next
From: Oleg Bartunov
Date:
Subject: Re: New structers for optimazing R-tree