0

I'm planning to add a GIS database to an existing PostgreSQL 12 cluster with multiple databases, streaming (hot standby) replication and WAL archiving.

Once created the new database will never be changed, and is easily recreated from the source data. However it would be very large (100s of GB).

The server is currently backed-up using wal-e (periodic base backups plus wal archiving) and has to use physical replication due to use of large objects.

Is there any way to exclude the new database from this process, so that the backups are not significantly slowed and inflated by the new data? It would still need to work for a replication though, making it an even more complex problem.

Is this something that can be done perhaps with tablespaces, which would then be manually copied for initial replications instead of using pg_basebackup?

Improve this question

1 Answer 1

Reset to default
4

No, there is no way to do that.

I would recommend that you create a second PostgreSQL cluster and put the database there. That does not incur a big overhead as far as system resources are concerned, and it will solve your problem.

Improve this answer
1
  • Just want to add point here. We need to consider this while tuning shared_memory and tune it accordingly.
    – pgyogesh
    Commented May 20, 2021 at 4:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.