Support for Preserving Tablespace Information During Synchronization

[seonghobae]

Hello,

First of all, thank you for developing PeerDB—it's a fantastic tool that's been incredibly helpful for our data synchronization needs.

I've noticed that when synchronizing data from a source PostgreSQL database, PeerDB does not consider the tablespace settings of the source tables. All tables and indexes in the destination database are created using the default tablespace settings, without preserving the tablespaces defined in the source.

Our use case relies on custom tablespaces for performance optimization and data organization across different storage systems. The absence of tablespace preservation means we need to manually adjust the tablespaces after synchronization, which is not ideal for automated workflows.

My questions are:

• Is there currently a way to have PeerDB preserve or replicate the tablespace settings from the source database during synchronization?
• If not, are there any plans to support tablespace consideration in future updates?
• Do you have any recommended workarounds for this issue in the meantime?

Your guidance on this matter would be greatly appreciated. Supporting tablespaces would enhance PeerDB's utility for users who rely on this PostgreSQL feature.

Thank you for your time and for developing such a valuable tool!

Best regards,

Seongho Bae

[heavycrystal]

Hi @seonghobae,
This is definitely an interesting (albeit niche) ask, and it should be possible. I'll update this issue as and when we decide to implement this, it should be in the medium term.