Dmitry Yemanov
Dmitry Yemanov
@mrgleba, could you please specify exactly the `database = ` part of replication.conf. And whether the db path is local or located on a NFS share.
It should look like `database = /my/db/path`
Funny. I was sure this is prohibited, but it seems likely to work, provided that the missing db name prefix is fixed.
I can confirm the primary side can work without per-database configuration settings. However, it's still impossible on the replica side, making the whole effort rather pointless.
OK, I will consider including the fix into the next v4 post-release.
No, this is not going to work for the replica side, database name must be specified explicitly there.
As far as I see, only sub-task #2058 (aka CORE-5338) remains not implemented. Do I get it right? Any plans about it?
Will the current suffix be preserved for official releases? Will the sha-hash be removed from the official releases? Would the sha-hash to removed also for non-GH official releases, e.g. for...
That limit serves two goals: (1) prevents infinite (or finite but risky due to possible stack overflow) recursion and (2) prevents resource leaks (query is not released but executed again...
Most of the `ALTER DATABASE` sub-commands are intentionally not replicated, but some others should be but currently not.