From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Joshua Brindle <method(at)manicmethod(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
Subject: | Re: 8SEPostgres WAS: .4 release planning |
Date: | 2009-01-26 23:11:42 |
Message-ID: | 87d4e9hdch.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua Brindle <method(at)manicmethod(dot)com> writes:
> Yes, I will look at them to the extent I am able. As I am not familiar with the
> postgresql codebase I won't be able to assert the correctness of the hook
> placement (that is, where the security functions are called with respect to the
> data they are protecting being accessed). The postgresql community should be
> more familiar with the hook call sites and hopefully can assist there.
I would suggest looking at the documentation (which I assume the patch does
update). If it's not clear that things are in order from the documentation
then either it needs better documentation or something's wrong...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2009-01-26 23:23:25 | Re: 8.4 release planning |
Previous Message | Ron Mayer | 2009-01-26 23:11:11 | Re: On SCM |