KaiGai Kohei writes:
> * Row-Update/Delete trigger mechanism allows user defined triggers
> to refer the older tuple updated/deleted.
> * The ACL_TRIGGER privilege allows normal users to set up triggers
> on the relation allowed.
> It means someone with ACL_TRIGGER can set up a trigger which
Tom Lane wrote:
> KaiGai Kohei writes:
>> * Row-Update/Delete trigger mechanism allows user defined triggers
>> to refer the older tuple updated/deleted.
>> * The ACL_TRIGGER privilege allows normal users to set up triggers
>> on the relation allowed.
>
>> It means someone with ACL_TRIGGER ca
Tom,
> Discuss the implications of changing such a GUC partway
> through this sequence. For extra credit, explain what would happen if
> it were set via ALTER ROLE SET for one role or the other.
>
> In short: -1 from me.
Heh. That's your best rejection yet. Someday I'll print out all the
reje
Vlad,
> It shows only top-level statements. You can see 'select * from f()' in
> this table but you never see what is actually executing in this function.
Queries executed inside functions are opaque to the stats collector for a
variety of technical reasons. Changing this is on the TODO list, b
On Thu, 2009-03-12 at 08:26 -0700, Josh Berkus wrote:
> Tom,
>
> > Discuss the implications of changing such a GUC partway
> > through this sequence. For extra credit, explain what would happen if
> > it were set via ALTER ROLE SET for one role or the other.
> >
> > In short: -1 from me.
>
> He
I have tried to find this within both the 8.3.6 docs and searches
within the mailing list archives, but I couldn't find anything.
I am new to postgresql, after having followed it from a distance for
quite a few years. I have used other systems quite a bit over the
years and this data was often av
Robert Morgan wrote:
I have tried to find this within both the 8.3.6 docs and searches
within the mailing list archives, but I couldn't find anything.
I am new to postgresql, after having followed it from a distance for
quite a few years. I have used other systems quite a bit over the
years a
Heikki, I updated the SE-PostgreSQL patches:
http://sepgsql.googlecode.com/files/sepgsql-core-8.4devel-r1714.patch
http://sepgsql.googlecode.com/files/sepgsql-utils-8.4devel-r1714.patch
http://sepgsql.googlecode.com/files/sepgsql-policy-8.4devel-r1714.patch
http://sepgsql.googlecode.com/files/sep
Hi,
I wish to implement a postgreSQL driver for a lisp-like language
[arclanguage.org] - it should speak the pg v2 text format protocol via
sockets I guess.
Im reading the v2 protocol spec, but it would be handy to trace the
exact text sent back and forth during a psql session - to help me
unders
Alvaro Herrera wrote:
Gregory Stark escribió:
Heikki Linnakangas writes:
KaiGai Kohei wrote:
* ACL_SELECT_FOR_UPDATE has same value with ACL_UPDATE, so SE-PostgreSQL
checks db_table:{update} permission on SELECT ... FOR SHARE OF,
instead of db_table:{lock} permission.
This again fall
Josh, this isn't a rejection. Both Tom and I asked for more exploration
of the implications of doing as you suggest. Tom has been more helpful
than I was in providing some scenarios that would cause problems. It is
up to you to solve the problems, which is often possible.
OK, well, barring th
How much of this pain would go away if we changed over to the arguably
correct (as in Or*cle does it that way) scoping for names, wherein the
parser first tries to match a name against column names of tables of the
current SQL statement, and only failing that looks to see if they are
plpgsql
On Thursday 12 March 2009 21:39:54 Josh Berkus wrote:
> > Josh, this isn't a rejection. Both Tom and I asked for more exploration
> > of the implications of doing as you suggest. Tom has been more helpful
> > than I was in providing some scenarios that would cause problems. It is
> > up to you to s
Gordon Anderson wrote:
I wish to implement a postgreSQL driver for a lisp-like language
[arclanguage.org] - it should speak the pg v2 text format protocol via
sockets I guess.
You probably should go straight to v3. v2 is quite old by now.
Im reading the v2 protocol spec, but it would be handy
14 matches
Mail list logo