PostgreSQL

10 December 2025 13:01

Yeah, except that the data will come from the secondary

PostgreSQL

10 December 2025 13:00

Switching two times the timelines

PostgreSQL

10 December 2025 12:59

btw - im aware of logical replication
im just playing around with physical replication now

PostgreSQL

10 December 2025 12:55

How can I achieve something like this? if it's even possible?
I thought in case it's part of replication slot it will save the last state to replicate from

PostgreSQL

10 December 2025 12:52

Removing the standby.signal will make the timelines diverge

PostgreSQL

08 December 2025 13:33

For low-volume low-reliability DBs — yes.

PostgreSQL

08 December 2025 12:20

Thanks, Jamie, it looks like 1 database per postgresql cluster is the best option.

PostgreSQL

08 December 2025 11:31

Hello everyone,

I’m new to PostgreSQL and would like to ask a beginner question.

Is it considered best practice to use a single PostgreSQL cluster to host multiple databases for different applications? From what I understand, all databases in a cluster share the same WAL stream, so I’m unclear how point-in-time recovery could be performed for an individual database within that cluster.

Also, RDBMS can be as fast as their transaction logs, are multiple databases add performance overhead to the single transaction log file compared just to have a single db on a particular cluster?

PostgreSQL

02 December 2025 13:18

I assume they didn't like our response

PostgreSQL

02 December 2025 13:17

Yes.

(My vote for permaban.)

PostgreSQL

02 December 2025 13:11

Did OP delete the question? Or am I just a bit dumb right now? 😅

PostgreSQL

02 December 2025 12:29

Feel free to use it, it might work, it would probably work

PostgreSQL

02 December 2025 12:16

The question is extremely meaningless.

Don't ask questions, write code.

(No, you cannot make architectural blueprints in areas you don't know anything about. Just write the system.)

PostgreSQL

02 December 2025 12:09

For example, consider something like Signal: it's very secure, they keep barely any data (and such data can also be sharded very effectively)

PostgreSQL

02 December 2025 12:01

It highly depends on the architecture.

PostgreSQL

10 December 2025 13:00

so this would be like just creating the table on the current master , no?

PostgreSQL

10 December 2025 12:59

You can, however, promote the secondary, create your tables, then make the primary a standby and sync it, then make the primary again primary, and switch back once again the secondary to make it secondary again

PostgreSQL

10 December 2025 12:58

There is no way to merge back to primary after the standby diverges, unless you use something like pg_rewind but that moves you back in time, it doesn't integrate the changes

PostgreSQL

10 December 2025 12:53

Corrected, timeline switch happens on promote

PostgreSQL

10 December 2025 12:51

Is it possible to remove the standby.signal from replica in order to create some tables only for replica, and then touch standby.signal and start the replica again? will it work? or it will damage the WAL order?

PostgreSQL

08 December 2025 13:25

Well in that case you will waste a little of ram because shared_buffer is assigned by one cluster and it tends to be a large memory segment. Every case has its drawbacks and your best choice will depend on your use case

PostgreSQL

08 December 2025 11:40

Point in time recovery impacts to the whole instance so you would recover every database.

PostgreSQL

02 December 2025 13:18

Supabase yes or no??

PostgreSQL

02 December 2025 13:18

Yes they did, check the history

PostgreSQL

02 December 2025 13:15

They came, they asked, they deleted and left

PostgreSQL

02 December 2025 12:30

I wouldn't use it because i don't like SaaS because of the added latency + complexity (postgresql is fairly easy and self contained to use), but some peoople like the trade off of paying money to not have to care about that

PostgreSQL

02 December 2025 12:22

A good relational database intro book would give you some general info.

PostgreSQL

02 December 2025 12:15

If you can afford it, sure

PostgreSQL

02 December 2025 12:04

The best way to keep data safe is to have as least of it as possible, or as Germans would say, "datensparsamkeit"

PostgreSQL

02 December 2025 10:21

PgBouncer is great if you need it. Which problem are you trying to fix?