1.31.0 crashes (after upgrade)

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

Baserow 1.31.0

If you are self-hosting, which installation method do you use to run Baserow?

Docker single image (both custom and standard configs)

What are the exact steps to reproduce this issue?

After upgrade from 1.30.1, Baserow fails to start (logs indicate a crash).
In my case this only seems to happen to instances which were first installed prior to version 1.30.1, but there may be other factors at play here (I don’t have enough test instances to draw any meaningful conclusions :smiley: about version impact - and I have not investigated this further yet)

The relevant part of the logs seems to be this:
[BACKEND][2025-02-10 13:29:32] return self.cursor.execute(sql)
[BACKEND][2025-02-10 13:29:32] ^^^^^^^^^^^^^^^^^^^^^^^^
[BACKEND][2025-02-10 13:29:32] django.db.utils.ProgrammingError: operator does not exist: integer = text
[BACKEND][2025-02-10 13:29:32] LINE 7: WHERE opt.id = "database_tab…
[BACKEND][2025-02-10 13:29:32] ^
[BACKEND][2025-02-10 13:29:32] HINT: No operator matches the given name and argument types. You might need to add explicit type casts.
2025-02-10 13:29:32,919 WARN exited: backend (exit status 1; not expected)
2025-02-10 13:29:32,919 WARN exited: backend (exit status 1; not expected)
2025-02-10 13:29:32,919 INFO gave up: backend entered FATAL state, too many start retries too quickly
2025-02-10 13:29:32,919 INFO gave up: backend entered FATAL state, too many start retries too quickly
2025-02-10 13:29:32,919 INFO reaped unknown pid 731 (exit status 0)
2025-02-10 13:29:32,919 INFO reaped unknown pid 731 (exit status 0)
Baserow was stopped or one of it’s services crashed, see the logs above for more details.

2

Hey @dev-rd,

thanks for bringing this to our attention. I’m not sure why this is happening at the moment, as this migration only involves fields with numbers, so integer = text shouldn’t occur at all.

Just to confirm: have you ever manually changed the column types in the database or performed any manual operations on the database (bypassing Baserow and using psql or other PostgreSQL clients directly)?

3

It would also be useful if you can share the full output logs, how you’re self-hosting Baserow exactly (which deployment method, commands to start, etc), and the environment variables you’ve configured. Can you also elaborate on the custom configs? Are those just environment variables, or did you extend Baserow with a plugin?

4

Hi, I’ve sent the logs via message.
by custom config I meant mostly environment variables. No plugins.