2e22d024-e200-4932-9308-1b11e749a068

You can't move GCP volumes to metal yet.

ah, are all the database prefab images on GCP?

I am not sure what you mean by this, but you can create new databases on metal if you have the related feature flag enabled. However, moving existing volumes to metal is not possible yet.

is the volume what's blocking the database from being created / moved in a different region then?

When I created my database I did so with "Add PostreSQL"

yes, the volume follows the service's region

for my app container I see all the new metal regions, etc, but for the database only the existing US West

this is indeed intended, as you can't move volumes from gcp to metal. your postgres database has been deployed on us-west gcp pre metal era.

The issue I'm running into there is that it doesn't seem like there's a way to specify the volume region before creating the database? Unless I'm missing something there, I'm assuming that I could use a Postgres Docker image instead of the pre-built database container, but I think that misses out on the Data viewer and then the automatic backup scheduling through railway if I upgrade to teams right?

you would still get the db features. still, it's odd that you're not allowed to specify a region on creation.

Oh cool, that's good to know

I'll play around with it some, I'm getting some latency in my app in prod and I'm trying to troubleshoot what the bottleneck is since on localhost it's really fast, and I mean on localhost there's no rtt latency so of course it's fast but I'm just trying to figure out what I can do to optimize that a bit in prod

alright, curious

!e

I forgor

Lemme raise this accordingly to the team- I think we would want people to set a default region.

seems like databases deploy automatically without staging a changeset based on the bit of messing around i just did

changing that could also fix it

New users can btw, with the new workspaces system

I just haven't migrated existing users

oh sweet, the preferred region now works when you have a workspace?

I told you a few days ago that db creation on metal is fucky <:kekw:788259314607325204>

working on it 😢

Thanks Angelo!

For now the fastest way is to eject a volume, move db service into a new region and attach a new volume there

And for transferring the data, pgdump/pgrestore it is

I'll spin up a test project to play around with some stuff to see how much performance benefits I can get before I start messing with my prod stuff, but really excited about bare metal! Love all the recent railway updates

even that didn't work for me.

1. I delete the Volume

2. This allows me to change the service region

3. But as soon as I attach a new volume the DB service jumps back to US-West

Lol what

<:wat:786868710791053312>

yeah. weird af

Ngl

Actually

it's as if volumes aren't supported at all outside of GCP US-West

Did you deploy the changes in between the volume detachment/reattachment?

yes

Okay I thought maybe you didn't

yeah, that's what i was thinking first

Then, no idea why it is behavin'

U also have priority boarding, right?

No, do i need it?

Not that I am sure that you do, but worth trying

Volumes in metal aren't supported at all without it?

It can be enabled from the Ctrl+k menu

They definitely are on priority

I have a pg instance in ewwrope on metal

lemme try again, this time with priority

I don't work at railway, so I can't be 100% certain

Yeah that explains it

Hmm with the priority boarding it really should not

If you go into your feature flags settings, make sure volumes on metal is on

!s