Veil http://pgfoundry.org/projects/veil is currently not a very good
Postgres citizen. It steals what little shared memory it needs from
postgres' shared memory using ShmemAlloc().

For Postgres 8.2 I would like Veil to be a better citizen and use only
what shared memory has been reserved for postgres add-ins.

So, I would like to propose:
1) that a new shared memory area for add-ins be created
2) that it should be accessible only to add-ins specifically requesting
its use
3) that the size of this add-in memory be controlled through a new GUC
setting

If this proposal is acceptable, I'd like some suggestions for naming the
GUC. If not we will be stuck with add_in_shmem, specified in Kbytes.

My expectation is that this would be a very small change and one that I
am probably competent to make myself, with a little review from my
friends.

__
Marc



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEbROmUBr6u+c2wkERAo74AJ9DjJYCV1tRX3fbHg+OUT dAaqXLxQCePNzG
UuYAA/UuKrPCTfhqfd/GxMY=
=JCIU
-----END PGP SIGNATURE-----

On Thu, 2006-05-18 at 17:39 -0700, Marc Munro wrote:

> For Postgres 8.2 I would like Veil to be a better citizen and use only
> what shared memory has been reserved for postgres add-ins.

How would Postgres ask the add-in how much memory it needs? How would
the add-in know how much has been reserved for it? How would an add-in
know whether it was the only add-in and whether it could take all of the
allocation?

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Marc Munro wrote:
> Veil http://pgfoundry.org/projects/veil is currently not a very good
> Postgres citizen. It steals what little shared memory it needs from
> postgres' shared memory using ShmemAlloc().
>
> For Postgres 8.2 I would like Veil to be a better citizen and use only
> what shared memory has been reserved for postgres add-ins.

Why should this be individually restricted? AFAICS Veil's functionality
would be essential to access row level ACL controlled tables, so if it
fails for low mem conditions it's much like a backend failure.

Regards,
Andreas

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq