Compare occurence of chars in PostgreSQL string
I have some data like this:
postgresql
How to fix unicode REPLACEMENT CHARACTER � in postgres database
Is there a way fix the � problem in postgres database:
How can I migrate data between 2 PostgreSQL clusters without auto-increment ID conflicts?
I have 2 database clusters that operate independently. In the future, I may need to move the records for a customer from cluster 1 to 2. I have a bash script where I do server-side copying of the table records into CSV files from cluster 1 and then restore them into cluster 2.
child to parent in same table – there must be a better way to do this
i want to relate child to parent from same table.
Can one dictate the order of generated values when adding a new BIGSERIAL column to a table?
I need to add a new BIGSERIAL column to a huge table (~3 billion records). This question is similar to what I need to do and the accepted answer has helped me somewhat. But I’m still wondering about something. In my case, the table already has a BIGSERIAL column which is the primary key, but many rows have been deleted so now there are gaps. (The table has subsequently been fully vacuumed.) I need to regenerate the values so that they are sequential again. Here are 5 example rows of what I want to achieve where the new_value > 1000:
Fuzzy searching through multiple fields in postgreSQL
I’ve to do fuzzy search on multiple fields (in an attempt to create something like autocomplete similar to product search in amazon).
I tried this through ElasticSearch but was wondering if there’s something equivalent to it in postgreSQL.
Trigger works for UPDATE, but for INSERT
In my database schema an organization can have multiple addresses but only one default address. I’m trying to create a trigger where if the is_default column is set to true on an insert or update, it sets the rest of the rows to false and the current one to true.
Table with smaller data types seems to take more space on disk?
I have these two identical tables:
PostgreSQL crash due to lack of device space
We run PostgreSQL 11 under a CentOS 7 server.
Recently, we had several warnings in the log that caused the PostgreSQL server to crash:
Collation won’t set when creating new database
I am trying to set the collation for a new database in PostgreSQL 13 but it does not seem to take effect: