Thanks Tom et al,
I appreciate the explanation.
I am certainly more appreciative of what is going on behind the scenes now
when I see 'tuple concurrently updated' errors.
I couldn't initially find a way to grant select on all present *and
future*tables in a schema, which is why we took the approac
Adrian Klaver writes:
> On 02/27/2014 06:54 PM, Jason Daly wrote:
>> When I attempt to execute the non-query "GRANT SELECT ON TABLE
>> . TO ", I occasionally encounter an exception from
>> postgresql, 'tuple concurrently updated'.
> My guess this is covered here:
> http://rhaas.blogspot.com/2013/
On 02/27/2014 06:54 PM, Jason Daly wrote:
Hi,
When I attempt to execute the non-query "GRANT SELECT ON TABLE
. TO ", I occasionally encounter an exception from
postgresql, 'tuple concurrently updated'.
I think the tuple it is referring to is the role.
Our app is multi-threaded, and it is very p
Hi,
When I attempt to execute the non-query "GRANT SELECT ON TABLE
. TO ", I occasionally encounter an exception from
postgresql, 'tuple concurrently updated'.
I think the tuple it is referring to is the role.
Our app is multi-threaded, and it is very possible for more than one thread
to be attem
