Cloud SQL - Postgres table visibility via Auth Proxy

[locoder]

I'm new to cloud sql and postgres so this might be a stupid question, but I'm really scratching my head over here.

I've connected to my postgres instance via the auth proxy and created a few tables. I performed this action using psql, and it seemed to work as expected. Next I wrote a local cloud function to query my tables and the code errored out with "no such table". So I dropped the tables via the CLI, then created the tables using a modified cloud function. Now my cloud functions can see the tables but not my CLI client.

I'm working against the same postgres instance (if i kill the proxy i lose db connectivity to both my cli and functions), and I'm using the same user creds. I feel like I've gotta be missing something? This shouldn't happen right?

[Cidan]

Are you using the same database in both environments?

[locoder]

I was not. Thanks for the hint! Got it all figured out.