Re: [PATCHES] [HACKERS] Contrib -- PostgreSQL shared variables

2004-08-25 Thread Rick Gigger
LockShared('name');
[EMAIL PROTECTED] wrote:
This is a first pass on a simple shared memory variable system for
PostgreSQL. I would appriciate anyone interested in this functionality to
rip it apart.
It basically adds this functionality:
SetShared('name', value);
GetSharedInt('name');
SetSharedText('name);
RemovedShared('name');
I also added two extra functions that are sort of a kludge, but could be
very helpful.
AddSharedInt('name', value);
SubSharedInt('name', value);
These add or subtect the 'value' from the variable and return the result.

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [PATCHES] [HACKERS] Contrib -- PostgreSQL shared variables

2004-08-25 Thread pgsql
 LockShared('name');

Hmmm, I thought about that, but it is *WAY* more complicated than it
looks. What if after a Lock the process crashes before it can call
Unlock? It is this problem that inspired the add and sub calls.




 [EMAIL PROTECTED] wrote:
 This is a first pass on a simple shared memory variable system for
 PostgreSQL. I would appriciate anyone interested in this functionality
 to
 rip it apart.

 It basically adds this functionality:

 SetShared('name', value);
 GetSharedInt('name');
 SetSharedText('name);
 RemovedShared('name');

 I also added two extra functions that are sort of a kludge, but could be
 very helpful.

 AddSharedInt('name', value);
 SubSharedInt('name', value);

 These add or subtect the 'value' from the variable and return the
 result.


 


 ---(end of broadcast)---
 TIP 9: the planner will ignore your desire to choose an index scan if
 your
   joining column's datatypes do not match



---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])