From: | momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: > Gavin Sherry <swm@linuxworld.com.au> writes: > > I ran across |
Date: | 2005-08-12 21:20:24 |
Message-ID: | 20050812212024.E27AB52EE3@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
> Gavin Sherry <swm(at)linuxworld(dot)com(dot)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...
Yeah, its not that exciting but that error message would throw your
average user.
I've attached a patch which calls CommandCounterIncrement() in each of the
grant loops.
Gavin Sherry
Modified Files:
--------------
pgsql/src/backend/catalog:
aclchk.c (r1.116 -> r1.117)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/aclchk.c.diff?r1=1.116&r2=1.117)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-08-12 21:23:10 | pgsql: [ backpatched to 8.0.X.] > >> 3) I restarted the postmaster both |
Previous Message | Bruce Momjian | 2005-08-12 21:09:34 | pgsql: More rsi assignment line too. |