Cannot View Some Tables or Input Data in some fields

Kimmy · February 22, 2026, 12:11am

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/baserow:2.1.0

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

Docker version 29.2.1, build a5c7197

What are the exact steps to reproduce this issue?

Start Baserow using Docker.
Clicked on a table. The view is gone.
I cannot enter data into some fields.

Attach screenshots, videos, or logs that demonstrate the issue.

petrs · February 23, 2026, 10:43am

Hi @Kimmy,

you should probably see some error in the logs, can you look for it and post it here?

Also, your steps to reproduce are probably missing some steps How did you create the table and view, and what did you do with the instance before seeing this error?

Kimmy · February 23, 2026, 4:58pm

The table and view was created months before I had this issue. That was why I didn’t add it as a step. I forgot to state is my steps that I updated Baserow to 2.1.0

Here is a copy of my log: [BACKEND][2026-02-23 16:50:37] File "/baserow/backend/src/baserow/api/decorat - Pastebin.com

picklepete · February 23, 2026, 5:05pm

Hi @Kimmy,

Do you know what version of PostgreSQL you are running?

Also, if you are able to, would you mind sharing the output of this SQL statement?

SELECT * FROM pg_timezone_names WHERE name = 'US/Eastern';

Judging by the error message, your PostgreSQL is missing some timezone data.

Cheers,

Peter Evans

Kimmy · February 23, 2026, 5:14pm

How do I tell which version of PostgreSQL I am running? I am using the Docker install version that comes with it already installed. And how Do I share the SQL statement?

Kimmy · February 26, 2026, 1:42am

Is there any new update for my issue?

picklepete · February 26, 2026, 9:27am

Good morning @Kimmy, my apologies for the delay in getting back to you.

No problem with skipping the SQL query, it was just an extra insight if you had the ability to execute it.

Looking at your error log, it definitely looks like the timezone issue is coming from your database. Did you by chance install the image differently at all? Or maybe make any changes to PostgreSQL?

I’m imagining you haven’t, but it’s worth checking! I’m a little stumped, to be honest. It’s a strange one. I may have to loop in some other developers…

Cheers,

Peter Evans

Kimmy · February 27, 2026, 1:44am

Hello! I didn’t install the image differently or made chances to PostgreSQL. The only change I made was going from 2.0.6 to 2.1.0 a few days ago. I can’t think of anything else

picklepete · February 27, 2026, 11:29am

Hi @Kimmy,

Thanks so much for your patience. We’ve identified the cause, and we’ll be releasing a patch later on today to resolve it.

Cheers,

Peter Evans

Kimmy · February 28, 2026, 2:49am

Hi @picklepete I updated to 2.1.3 but Baserow keeps restarting.

Kimmy · March 5, 2026, 8:54pm

@picklepete is there any update for my issue? I tried updating to 2.1.4 but I am still running into issues.

picklepete · March 6, 2026, 9:30am

Hi @Kimmy , my apologies for the delay in getting back to you.

The issue was merged and released in v2.1.3, we were able to successfully use US/Eastern in that fix.

Judging by the latest error message, you’re facing a different problem. Specifically this:

 [REDIS][2026-02-28 02:42:32] <jemalloc>: Unsupported system page size  
 [REDIS][2026-02-28 02:42:32] <jemalloc>: Unsupported system page size

Would you mind sharing what OS/architecture you’re deploying Baserow in? It looks like you have an unusual/non-standard memory page size. You can retrieve it with getconf PAGESIZE (if you’re on Linux).

Cheers,

Peter Evans

Kimmy · March 6, 2026, 7:18pm

Hi @picklepete I ran the command and got this 16384

picklepete · March 11, 2026, 4:48pm

Thanks @Kimmy, can you share the OS/architecture too?

If you’re using an ARM-based system (e.g. newer Apple Silicon Macs / Linux servers), it looks like 16KB page sizes aren’t supported, only 4KB.

If you’re able to, you might have better luck:

Using an exernal Redis service (and changing REDIS_URL to point to it) configured for your needs, or
Swapping to an Alpine-based Redis image instead, or
If you are on an ARM-based system, installing Baserow elsewhere.

Cheers,

Peter Evans

Kimmy · March 12, 2026, 3:55am

Hello, @picklepete the OS/architecture I’m using is 64-bit ARM. I will take your advice

Kimmy · March 12, 2026, 4:44am

@picklepete I tried exporting my data in Baserow and importing it to another platform, but I am getting an error “Could not connect to the API server”.