Scaling up postgres memory scales shared-buffers without intervention

,
1

I am following the docs for Scale Postgres VMs.

I had a shared-256mb machine, and with fly postgres config show I got

shared-buffers            	3200   	8kB

I ran fly machine update ID --memory 2048 --app APPNAME, and checked the postgres config again:

shared-buffers            	65536  	8kB

I don’t mind that the postgres config was updated for me automatically, but the docs seem to indicate that this is something I have to do manually and be careful about.

Wondering if this is a bug in docs or unexpected behaviour.

1 Like
2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.