Profiles

A moved organization's rows always live in its own database. Its profile decides how statements reach them.

Profile	Path
fdw	every statement goes to the cloud Postgres, which reaches the organization's database through postgres_fdw
fdw+direct	statements that touch only this organization's tables go straight to its database through the tunnel; the rest go through postgres_fdw
direct	no postgres_fdw path; statements the direct path cannot take are refused with the reason

A moved organization pays for distance: its latency is almost linear in the round-trip time to its database. In our measurement at 43 ms, a read took 352 ms through fdw and 133 ms through fdw+direct; an update 351 and 89 ms (performance). The direct path skips the extra round trips of postgres_fdw, which is why it matters for organizations far from the cloud. lokadb check forecasts the latency before you move anyone.

Switch with lokadb org-profile -db CLOUD -org 1 fdw+direct; the details, the roles the direct path needs and cooperative mode are in profiles and cooperative mode.