PostgreSQL: Access to performance tuning options [116831641]

Assigned

Feature Request

Status Update

No update yet.

Description

be...@urbansharing.com

created issue #1

Sep 28, 2018 09:19AM

For some workloads and datasets, the default tuning in CloudSQL for Postgres is suboptimal. It'd be helpful to allow tuning by having access to change (at least) the following settings, in prioritised order:

work_mem
max_connections
shared_buffers

cpu_tuple_cost
cpu_index_tuple_cost

(The latter two given that we can't make good assumptions about the storage subsystem to meaningfully adjust seq_page_cost, random_page_cost and effective_io_concurrency.)

checkpoint_*
parallel_tuple_cost
parallel_index_tuple_cost
max_parallel_workers_per_gather

Comments

oa...@google.com <oa...@google.com> #2Sep 29, 2018 12:40AM

Assigned to gc...@google.com.

I have forwarded your request to our engineering team. I cannot provide an E.T.A. or guarantee that this feature will be deployed. Rest assured that your feedback is always seriously taken. Any future updates will be posted on this thread.

cp...@google.com <cp...@google.com> #3Oct 11, 2018 10:05AM

Is there any progress with that feature request?

[Deleted User] <[Deleted User]> #4Apr 28, 2020 09:08PM

I'm also very interested in having this extension in cloudsql for postgres since it's blocking the emigration of one of ours databases

ef...@conservation.org <ef...@conservation.org> #5Feb 8, 2021 05:43PM

+1 to voting for the ip4r extension. Currently not supported in Cloud SQL and we make use of it.

ba...@google.com <ba...@google.com> #6Aug 28, 2021 09:56PM

Any updates on this? It's blocking a migration from RDS to google cloud.

ba...@google.com <ba...@google.com> #7Aug 28, 2021 09:57PM

This is now supported on Cloud SQL: https://cloud.google.com/sql/docs/postgres/extensions#data-type-extensions

de...@ncr.com <de...@ncr.com> #8Aug 2, 2022 07:22AM

Any updates on the "effective_io_concurrency" ?

al...@google.com <al...@google.com> #9Jun 19, 2023 03:59PM

Hi team, any updates on the effective_io_concurrency ?