On Sun, 28 Aug 2011 18:20:31 +0300, Vlad Khorsun
hv...@users.sourceforge.net wrote:
Certainly, we can make API look like we _do_ join a new attachment to
an
existing distributed transaction. To do so we just start new
transaction
in API call internally (need to know TPB...) and join it with
On Mon, Aug 29, 2011 at 1:14 AM, Adriano dos Santos Fernandes
adrian...@gmail.com wrote:
All,
After I bought a new machine, I reinstalled Ubuntu in new HDD with ext4
filesystem.
While the new machine has much better CPU than the old one, I noticed
the build being very slow where Firebird
On 29/08/2011 06:27, Paul Reeves wrote:
On Monday 29 August 2011 at 11:05 marius adrian popa wrote:
you are not the only one that observed db/vm performance issues with ext4
maybe you need to mount it with data=writeback
On 29/08/2011 06:05, marius adrian popa wrote:
On Mon, Aug 29, 2011 at 1:14 AM, Adriano dos Santos Fernandes
adrian...@gmail.com wrote:
All,
After I bought a new machine, I reinstalled Ubuntu in new HDD with ext4
filesystem.
While the new machine has much better CPU than the old one, I
В Вс., 28/08/2011 в 19:14 -0300, Adriano dos Santos Fernandes пишет:
All,
After I bought a new machine, I reinstalled Ubuntu
11.04?
in new HDD with ext4
filesystem.
While the new machine has much better CPU than the old one, I noticed
the build being very slow where Firebird was
В Пн., 29/08/2011 в 07:47 -0300, Adriano dos Santos Fernandes пишет:
On 29/08/2011 06:27, Paul Reeves wrote:
On Monday 29 August 2011 at 11:05 marius adrian popa wrote:
you are not the only one that observed db/vm performance issues with ext4
maybe you need to mount it with
On Monday 29 August 2011 at 12:47 Adriano dos Santos Fernandes wrote:
On 29/08/2011 06:27, Paul Reeves wrote:
On Monday 29 August 2011 at 11:05 marius adrian popa wrote:
you are not the only one that observed db/vm performance issues with
ext4 maybe you need to mount it with data=writeback
В Пн., 29/08/2011 в 14:16 +0200, Paul Reeves пишет:
On Monday 29 August 2011 at 12:47 Adriano dos Santos Fernandes wrote:
On 29/08/2011 06:27, Paul Reeves wrote:
On Monday 29 August 2011 at 11:05 marius adrian popa wrote:
you are not the only one that observed db/vm performance issues
On Monday 29 August 2011 at 14:22 Alexander Peshkov wrote:
Paul, telling true I've also not understood a humor. May be that's
because I and Adriano are not native english speakers?
Probably :-) I can't say for other langauges but irony is used a lot in
english. When we say someone or
It´s semi OT, but what about using XFS?
Seems to be much better in terms of speed, not sure in terms of reliability:
http://www.slideshare.net/ibsurgeon/firebird-25-benchmark-by-tsutomu-hayashi-tomneko
Regards!
El 28/08/2011 07:14 p.m., Adriano dos Santos Fernandes escribió:
All,
After I
On 29/08/2011 10:13, Paul Reeves wrote:
On Monday 29 August 2011 at 14:25 Michael Weissenbacher wrote:
But if barriers are needed just to make journal commits safe on the disk
with write cache turned on this seems to be not directly related with
firebird databases - write cache ON will anyway
On 29/08/2011 10:24, Paul Reeves wrote:
On Monday 29 August 2011 at 13:35 Alexander Peshkov wrote:
Tested CREATE DATABASE on my old box. To avoid disk fragmentation
effects database was always created on new shining partition.
I've found different results doing a large db restore. ext4 came
On Monday 29 August 2011 at 15:27 Adriano dos Santos Fernandes wrote:
The default for ext3/4 is data=ordered and, from the kernel docs:
I read divergent things about this. Some says that ext3 default changed
to writeback, others says it depends from a kernel configure option.
I haven't
В Пн., 29/08/2011 в 16:11 +0200, Paul Reeves пишет:
The levels are
Application - we can set FW=ON or OFF. If ON the we are saying write
everything to disc immediately. If FW=OFF then we see a massive performance
gain on small test runs (especially if super* is used.)
Filesystem - ext3
В Пн., 29/08/2011 в 13:09 -0300, Adriano dos Santos Fernandes пишет:
On 29/08/2011 08:35, Alexander Peshkov wrote:
В Вс., 28/08/2011 в 19:14 -0300, Adriano dos Santos Fernandes пишет:
All,
After I bought a new machine, I reinstalled Ubuntu
11.04?
Yes. Kernel is 2.6.38.
We have
add built-in context variables 'PROC_NAME' and 'ERROR_LINE' and database level
trigger that fires on any ERROR
--
Key: CORE-3587
URL:
More detail in message wrong page type
Key: CORE-3588
URL: http://tracker.firebirdsql.org/browse/CORE-3588
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Hi,
In FB 2.1 I find it frustrating that FB can't use the FK index in
queries like this:
update Child
set Something = 'New stuff'
where MasterId in (
select Id
from Master
where OtherThing = 'SoughtValue'
)
I know this can be constructed in a few other ways, e.g. using an
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
application server). If I read the spec correctly, it is expected that a
Look at isc_prepare_transaction2() API. It could attach *any*
application-specific
message to the local transaction before actual commit. TM could pass XID +
something
to identify this part of distributed transaction into
isc_prepare_transaction and later read
this info back from
On Mon, Aug 29, 2011 at 5:57 PM, Vlad Khorsun
hv...@users.sourceforge.netwrote:
Another issue here is that when a non-recoverable error
happens (e.g. request synchronisation error),
Hmm... is it unrecoverable error ? BTW, request synchronisation error
could happen only
at fetching
30.08.2011 0:44, Kjell Rilbe wrote:
Has this been improved since FB 2.1?
Nope.
Any future plans?
In FB3, perhaps.
Dmitry
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management
22 matches
Mail list logo
