Rebound application doesn't have access to existing tables

[paul-mulvihill]

Hi.
I'm seeing the following behaviour and wondering if it's known/expected or something I've not setup right..

I setup an application and bind it to a new postgres instance.. that is fine.

• It makes the sb database
• Creates the sb user
  setups up any tables needed.
• all good.

I then unbind the application from the database instance.

• SB User is removed
• Table ownership is transferred to default account (cf)
  ok

I then try to rebind the application (or a new one) to the same database instance.

• a new sb username is created

I see the code grants all privileges to the database for the new sb user although this doesn't seem to be enough for any applications i've tried to actually start up.

When i manually alter the tables and put the owner to the new sb user it's happy. but this isn't a scalable solution.

Have you come across this before with the broker and is there a known resolution or is this something new?

Thanks

Paul

[paul-mulvihill]

Anyone monitoring these issues and able to offer any idea around this issue?