On 06/01/2016 04:06 PM, Adriano dos Santos Fernandes wrote:
> On 01/06/2016 08:18, Alex Peshkoff wrote:
>> Particularly lock files are not a problem - each database has own lock
>> file, and certainly same database can't be accessed with 2 engines
>> supporting different major ODS.
>> But we have a
On 01/06/2016 08:18, Alex Peshkoff wrote:
> Particularly lock files are not a problem - each database has own lock
> file, and certainly same database can't be accessed with 2 engines
> supporting different major ODS.
> But we have a number of other shared files (trace, mapping change
> notifica
01.06.2016 13:18, Alex Peshkoff wrote:
> But we have a number of other shared files (trace, mapping change
> notification, may be else). I see that trace name includes ODS version
> name (fb12_trace). The only problem that opened database is ODS13 ;)
> I.e. that issue worth to be checked and fixed.
On 06/01/2016 01:59 PM, Adriano dos Santos Fernandes wrote:
> On 01/06/2016 06:46, Dmitry Yemanov wrote:
>> 01.06.2016 12:40, Roman Simakov wrote:
>>
>>> Does it make sense to install several previous engines with current
>>> one to make it possible to perform B/R after server upgrade?
>> Sure, why
01.06.2016 14:06, Adriano dos Santos Fernandes wrote:
> But if databases is said to be "shared", two engines will access and
> corrupt them.
No, two engines will synchronize their access using the same lock table.
If one of them cannot read that lock table, it will fail. But no
corruption will
01.06.2016 13:06, Adriano dos Santos Fernandes wrote:
> But if databases is said to be "shared", two engines will access and
> corrupt them.
No, one engine will throw error about unsupported ODS.
--
WBR, SD.
--
Wh
On 01/06/2016 08:02, Dimitry Sibiryakov wrote:
> 01.06.2016 12:59, Adriano dos Santos Fernandes wrote:
>> How that will work if, for example, lock file version changes in a newer
>> engine?
>Lock files are separate for each database. One database cannot be accessed
> by two engines.
>
But if d
01.06.2016 12:59, Adriano dos Santos Fernandes wrote:
> How that will work if, for example, lock file version changes in a newer
> engine?
Lock files are separate for each database. One database cannot be accessed
by two engines.
--
WBR, SD.
--
On 01/06/2016 06:46, Dmitry Yemanov wrote:
> 01.06.2016 12:40, Roman Simakov wrote:
>
>> Does it make sense to install several previous engines with current
>> one to make it possible to perform B/R after server upgrade?
> Sure, why not. But it should be up to DBAs, I doubt we should distribute
>
On 06/01/2016 01:30 PM, Dimitry Sibiryakov wrote:
> 01.06.2016 12:24, Alex Peshkoff wrote:
>> 2 different libstdc++ do not work in same process.
> Oh, I forgot about Linux symbol hell.
>
Yes, oriented to source distribution it badly supports old binaries.
01.06.2016 12:24, Alex Peshkoff wrote:
> 2 different libstdc++ do not work in same process.
Oh, I forgot about Linux symbol hell.
--
WBR, SD.
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and
On 06/01/2016 12:53 PM, Dimitry Sibiryakov wrote:
> 01.06.2016 11:50, Alex Peshkoff wrote:
>> Only in a case if we use incompatible c++ compilers making impossible to
>> use fb3 provider library in fb4.
> Aren't plugins supposed to be compiler-independent?.. Existence of
> Firebird.pas means
>
01.06.2016 11:50, Alex Peshkoff wrote:
> Only in a case if we use incompatible c++ compilers making impossible to
> use fb3 provider library in fb4.
Aren't plugins supposed to be compiler-independent?.. Existence of
Firebird.pas means
that it can be written even in pascal...
--
WBR, SD.
On 06/01/2016 12:46 PM, Dmitry Yemanov wrote:
> 01.06.2016 12:40, Roman Simakov wrote:
>
>> Does it make sense to install several previous engines with current
>> one to make it possible to perform B/R after server upgrade?
> Sure, why not. But it should be up to DBAs, I doubt we should distribute
01.06.2016 12:40, Roman Simakov wrote:
> Does it make sense to install several previous engines with current
> one to make it possible to perform B/R after server upgrade?
Sure, why not. But it should be up to DBAs, I doubt we should distribute
engine12 inside the FB4 packages.
Dmitry
--
2016-06-01 10:53 GMT+03:00 Dmitry Yemanov :
> I've bumped the ODS version for v4. It cannot work with ODS12 databases
> anymore, backup/restore is needed.
Does it make sence to install several previous engines with current
one to make it possible to perform B/R after server upgrade?
--
Roman Sim
All,
I've bumped the ODS version for v4. It cannot work with ODS12 databases
anymore, backup/restore is needed.
Now we may introduce incompatible changes, some of them are expected
soon. Ideally, I'd prefer low-level changes to settle before September,
minor system table changes may be postpon
17 matches
Mail list logo
