SEO

#1 (**permalink**) 04-11-2008, 05:01 AM

Hi all,

I ran across this yesterday on HEAD:

template1=# grant select on foo, foo to swm;
ERROR: tuple already updated by self

We could do away with the error by producing a unique list of object names
-- but that would impose an extra cost on the common case. It seems to me
that producing a useful error message would entail the same cost, however.

Thoughts?

Gavin

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

#2 (**permalink**) 04-11-2008, 05:01 AM

Gavin Sherry <swm@linuxworld.com.au> writes:
> I ran across this yesterday on HEAD:

> template1=# grant select on foo, foo to swm;
> ERROR: tuple already updated by self

Seems to fail similarly in every version back to 7.2; probably further,
but that's all I have running at the moment.

> We could do away with the error by producing a unique list of object names
> -- but that would impose an extra cost on the common case.

CommandCounterIncrement in the GRANT loop would be easier, likely.
I'm having a hard time getting excited about it though...

regards, tom lane

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

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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Duplicate object names in GRANT