13.10.2021 15:44, Dimitry Sibiryakov wrote:
Vlad Khorsun wrote 13.10.2021 14:39:
Due to this, I see no reason to replicate physical
layout of master database to the replica. I.e. TABLESPACE-related statements
should not be replicated at all, IMO. Other opinions ?
I fully agree with not repl
Vlad Khorsun wrote 13.10.2021 14:39:
Due to this, I see no reason to replicate physical
layout of master database to the replica. I.e. TABLESPACE-related statements
should not be replicated at all, IMO. Other opinions ?
I fully agree with not replicated "CREATE/ALTER/DROP TABLESPACE" but what
13.10.2021 13:14, Dimitry Sibiryakov wrote:
About moving of tablespaces and objects between tablespaces: on primary site it succeeded, on synchronous replica it failed (and
vice versa). How such situation is going to be handled?
Tablespace is a concept about physical layout of data. It is
ср, 13 окт. 2021 г. в 15:25, Dimitry Sibiryakov :
> Roman Simakov wrote 13.10.2021 14:20:
> > I suppose you mean async replication. I guess like other errors, no?
>
>No, I meant exactly synch replication. "Other errors" in such cases
> leads to
> transaction rollback on both sides. Can tablesp
Roman Simakov wrote 13.10.2021 14:20:
I suppose you mean async replication. I guess like other errors, no?
No, I meant exactly synch replication. "Other errors" in such cases leads to
transaction rollback on both sides. Can tablespace moving to be rolled back?
--
WBR, SD.
Firebird-Deve
ср, 13 окт. 2021 г. в 13:15, Dimitry Sibiryakov :
>About moving of tablespaces and objects between tablespaces: on primary
> site
> it succeeded, on synchronous replica it failed (and vice versa). How such
> situation is going to be handled?
>
I suppose you mean async replication. I guess lik
Hi,
Dne 12. 10. 21 v 15:21 Dimitry Sibiryakov napsal(a):
BACKUP:
Backup of separate partition is something nobody asked for so far. At
least I cannot remember a ticket for gbak accepting filter condition
inside of a table, only filter for whole tables and (since it is already
implement
Den 2021-10-12 kl. 14:05, skrev Dmitry Yemanov:
12.10.2021 13:36, Kjell Rilbe wrote:
Support for many page sizes requires changes in page cache
management and should
be considered together. I don't see it as "must have" feature, btw.
That's the feature that our DB would benefit most from pr
About moving of tablespaces and objects between tablespaces: on primary site
it succeeded, on synchronous replica it failed (and vice versa). How such
situation is going to be handled?
--
WBR, SD.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/
Roman Simakov wrote 12.10.2021 16:30:
It allows you to restore tablespace contents to new places.
If the option is not specified gbak will use old locations for every
tablespace.
I still think this should be an explicit option as well, otherwise
surprising things - for the user - can happen when
10 matches
Mail list logo
