Re: [SQL] PLpgSQL variables persistance between several functions calls

From: Viktor Bojović <viktor(dot)bojovic(at)gmail(dot)com>
To: "Charles N(dot) Charotti" <ccharotti(at)yahoo(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] PLpgSQL variables persistance between several functions calls
Date: 2011-05-03 11:01:12
Message-ID: BANLkTinjBmTvgbpDXvb8y1RBTLrMfeE5eQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice pgsql-sql

the best way is to put all calls into one function and store values to
variables..

if that is not suitable you can try the way (which im not sure if anyone
uses) and it is to store values to sequences if value type is integer.
for other formats you will have to do conversions.
but im not sure if sequence values are stored in database or in memory.
that way will make your results visible to all sessions.

On Mon, May 2, 2011 at 11:43 PM, Charles N. Charotti <ccharotti(at)yahoo(dot)com>wrote:

> Hello everybody !
>
> I want to know if I could share PLpgSQL variables between different
> functions and within different calls just using memory (not tables or other
> methods).
>
> If it is really possible ?
>
> Thanks in advance,
>
> Chuck
>

--
---------------------------------------
Viktor Bojović
---------------------------------------
Wherever I go, Murphy goes with me

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Simon Riggs 2011-05-03 12:07:39 Re: Can we Flush the Postgres Shared Memory ?
Previous Message raghu ram 2011-05-03 10:54:34 Can we Flush the Postgres Shared Memory ?

Browse pgsql-sql by date

  From Date Subject
Next Message Grzegorz Szpetkowski 2011-05-03 12:41:39 Re: BINARY and BINARY VARYING datatypes in PostgreSQL
Previous Message Willy-Bas Loos 2011-05-03 10:20:47 Re: [SQL] PLpgSQL variables persistance between several functions calls