On 30-08-2011 18:27, Fulvio Senore wrote:
>
> Now I have installed Ubuntu 10.04 LTS 64 bit in my laptop, formatting
> the disk partitions with the ext4 file system.
> When I use the same program to open my catalog, it takes about 23
> seconds. That is in incredibly long time and I really cannot
I have read a recent thread about ext4 being slower than ext3, and I
have just discovered another problem.
I have developed an open source program that catalogs digital images:
all the information, included image thumbnails, are stored in a single
database. My own database contains almost 2
show proper info in rdb$index_segments.rdb$statistics for GTT (from index root
page)
Key: CORE-3590
URL: http://tracker.firebirdsql.org/browse/CORE-3590
Project: Fir
Internal shared resource leak
-
Key: CORE-3589
URL: http://tracker.firebirdsql.org/browse/CORE-3589
Project: Firebird Core
Issue Type: Bug
Environment: MacOS, FreeBSD
Reporter: Alexander Peshk
>> Look also at isc_reconnect_transaction() API which allows to
>> re-connect to the in-limbo
>> transaction at recovery phase and finally commit or rollback it.
>
> As far as I have seen, this is already done in Jaybird.
Very good.
> So the commit can
> be done from any connection,
On Mon, 29 Aug 2011 23:34:21 +0200, Roman Rokytskyy
wrote:
> This code should be already working in Jaybird since day 0 (David Jencks
> implemented it in the first version of the driver). The recovery process
> uses message to query the in-limbo transactions, is able to join them
> and is able
On Tue, 30 Aug 2011 00:17:19 +0300, "Vlad Khorsun"
wrote:
>> The XA semantics are a bit complicated, but essentially the database is
a
>> Resource Manager (RM), and a distributed transaction is assigned an Xid
>> by
>> the Transaction Manager (eg in the case of JavaEE it could be the
>> applicatio
