From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Volkan YAZICI <yazicivo(at)ttnet(dot)net(dot)tr> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Preserving Cluster-Wise Data |
Date: | 2006-12-05 18:06:18 |
Message-ID: | 4575B51A.9070709@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Volkan YAZICI wrote:
> Hi,
>
> I was taking a look at _SHARED variable implementation of different
> PLs and it looks like every PL implements its own ad-hoc method to
> preserve cluster-wise data. Wouldn't it be beneficial to have a
> cluster-wise table (sytem catalog?) which is accessible by any
> procedure with required (superuser?) privileges? With such a table,
> procedures (and PLs) will be able to preserve their state data
> natively without need of any ad-hoc method and because of we're using
> a just yet another plain table, all of the MVCC related stuff will be
> handled by PostgreSQL easily.
>
>
The data might well be PL and session specific, though. e.g. a perl
function ref would be both.
I don't know what state we would want to preserve across sessions anyway.
Let's see a use case that a plain user level table wouldn't serve.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-12-05 18:06:35 | Re: Weak passwords and brute force attacks |
Previous Message | Gregory Stark | 2006-12-05 17:59:54 | Re: old synchronized scan patch |