-Original Message-
From: Vlad Khorsun [mailto:hv...@users.sourceforge.net]
Sent: Lunes, 09 de Mayo de 2011 6:07
To avoid contention on common dbb_pool its usage was
replaced by att_pool when
possible. To make this task slightly easy there was
introduced
13.05.2011 9:43, Russell R wrote:
This post is related to the following 2 reported incidents:
http://tracker.firebirdsql.org/browse/CORE-3121
http://firebird.1100200.n4.nabble.com/Error-Restoring-v2-1-Database-to-v2-5-td2994314.html
The error is caused when you are running a 2.5 server, but
-Original Message-
From: Vlad Khorsun [mailto:hv...@users.sourceforge.net]
Sent: Lunes, 09 de Mayo de 2011 6:07
To avoid contention on common dbb_pool its usage was
replaced by att_pool when
possible. To make this task slightly easy there was
introduced
On 05/13/11 09:43, Russell R wrote:
This post is related to the following 2 reported incidents:
http://tracker.firebirdsql.org/browse/CORE-3121
http://tracker.firebirdsql.org/browse/CORE-3121
http://firebird.1100200.n4.nabble.com/Error-Restoring-v2-1-Database-to-v2-5-td2994314.html
On 13.05.2011 08:38, Dmitry Yemanov wrote:
13.05.2011 9:43, Russell R wrote:
Is there
any way to restore the backup to a database?
I'm afraid no, unless you drop the RDB$ADMIN role before backing up with
v2.1 gbak.
I was able to restore the test backup after using a hex-editor to rename
-=| marius adrian popa, Tue, May 10, 2011 at 01:35:00PM +0300 |=-
I have merged the following patches
sparc-no-m32.patch
powerpc-no-mcpu.patch
I review now the follwing that was needed for sh port
atomic_ops_require_cas.patch
From the list of patches
