Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL best practices compliance #8191

Open
frcroth opened this issue Nov 13, 2024 · 2 comments
Open

PostgreSQL best practices compliance #8191

frcroth opened this issue Nov 13, 2024 · 2 comments

Comments

@frcroth
Copy link
Member

frcroth commented Nov 13, 2024

The people who made PostgreSQL have created this document: https://wiki.postgresql.org/wiki/Don%27t_Do_This#Text_storage

Some things I noticed

  • Char should never be used -> We use it a lot
  • Varchar(n) should probably not be used -> We use it

Opinions on this @fm3 ?

@fm3
Copy link
Member

fm3 commented Nov 13, 2024

Yeah, I saw the document too yesterady, but didn’t read through it yet. We should go through it at some point and consider what we should change (and probably not just text).

I think it doesn’t have super high priority, though. After all, we’ve been sailing fairly smoothly so far with our db.

@fm3
Copy link
Member

fm3 commented Nov 13, 2024

Looks like we are guilty of

I always thought that we should probably eventually move our timestamptz fields to timestamp (without timezone), as they are all utc anyway, but apparently that is not true

@fm3 fm3 changed the title PostgreSQL text storage best practice compliance PostgreSQL best practices compliance Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants