pg_stat_statements_reset() permission denied on Google Cloud SQL
up vote
2
down vote
favorite
Main Issue
I'm unable to execute the function SELECT pg_stat_statements_reset();
in order to profile changes in query optimization due to insufficient permissions.
The error message reads:
permission denied for function pg_stat_statements_reset
I would like to know if there are any other ways to reset the pg_stats on Cloud SQL?
Environment
- PG version: PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, 64-bit
- Platform: Google Cloud SQL
- User: default postgres user with
cloudsqlsuperuser
role
Attempted Steps
I have found a previous answer on this topic which suggested that pg_stat_statements_reset()
should work from the default postgres user created through the cloud console. However, the listed solution does not work, it returns the same permission denied error
Related Question
postgresql google-cloud-sql
add a comment |
up vote
2
down vote
favorite
Main Issue
I'm unable to execute the function SELECT pg_stat_statements_reset();
in order to profile changes in query optimization due to insufficient permissions.
The error message reads:
permission denied for function pg_stat_statements_reset
I would like to know if there are any other ways to reset the pg_stats on Cloud SQL?
Environment
- PG version: PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, 64-bit
- Platform: Google Cloud SQL
- User: default postgres user with
cloudsqlsuperuser
role
Attempted Steps
I have found a previous answer on this topic which suggested that pg_stat_statements_reset()
should work from the default postgres user created through the cloud console. However, the listed solution does not work, it returns the same permission denied error
Related Question
postgresql google-cloud-sql
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Main Issue
I'm unable to execute the function SELECT pg_stat_statements_reset();
in order to profile changes in query optimization due to insufficient permissions.
The error message reads:
permission denied for function pg_stat_statements_reset
I would like to know if there are any other ways to reset the pg_stats on Cloud SQL?
Environment
- PG version: PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, 64-bit
- Platform: Google Cloud SQL
- User: default postgres user with
cloudsqlsuperuser
role
Attempted Steps
I have found a previous answer on this topic which suggested that pg_stat_statements_reset()
should work from the default postgres user created through the cloud console. However, the listed solution does not work, it returns the same permission denied error
Related Question
postgresql google-cloud-sql
Main Issue
I'm unable to execute the function SELECT pg_stat_statements_reset();
in order to profile changes in query optimization due to insufficient permissions.
The error message reads:
permission denied for function pg_stat_statements_reset
I would like to know if there are any other ways to reset the pg_stats on Cloud SQL?
Environment
- PG version: PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, 64-bit
- Platform: Google Cloud SQL
- User: default postgres user with
cloudsqlsuperuser
role
Attempted Steps
I have found a previous answer on this topic which suggested that pg_stat_statements_reset()
should work from the default postgres user created through the cloud console. However, the listed solution does not work, it returns the same permission denied error
Related Question
postgresql google-cloud-sql
postgresql google-cloud-sql
asked Nov 8 at 3:01
Sean Yuan
112
112
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53200947%2fpg-stat-statements-reset-permission-denied-on-google-cloud-sql%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown