I'm trying to set the exclusions for one of our servers and I see Firebird
running.
I don't have any experience with this program and I was hoping someone on the
forum could shed some light on the needed exclusions.
Any help would be greatly appreciated.
Thanks Tim
as I can install firebird 3 superclasic in linux?
I want to try it on devuan
Best Regards
| ISMAEL |
Hi Sergio,
Definitely there should transaction which produces conflict, probably
your query does not catch it.
You can track it with Monlogger - download HQbird, install it and
register as trial (14 days), then connect with MonLogger to your
database and at the moment of error message click
sorry, I just copied a part of the select in the message. I do include that
flag in the actual select.
Here it is the complete select. I'm sending '-1' in "in_trans"
select
ma.mon$attachment_id,
mt.mon$transaction_id,
ma.mon$server_pid,
Hi,
chow do you check that transaction is readonly?
in your select this field is not included
regards,
karol Bieniaszewski
W dniu 2016-04-05 15:29:11 użytkownik shg_siste...@yahoo.com.ar
[firebird-support] napisał:
Hello! I'm having a problem which I
Hello! I'm having a problem which I don't undestand. I'm getting a deadlock
error in my app, but when I see the active transactions (I attach the select
I'm using) I see all read-only transactions active.
So, the question is: How can I get a deadlock error when I have just read-only
On 2016-04-04 9:08, Hasnain Najafi hasnain.naj...@boots.co.uk
[firebird-support] wrote:
> unsubscribe
>
> Regards,
>
> HARDWARE REFRESH TEAM
To unsubscribe send a mail to
firebird-support-unsubscr...@yahoogroups.com with subject: Unsubscribe
Mark
On 2016-04-05 10:47, Alex Castillo acr_k...@yahoo.com
[firebird-support] wrote:
> Hello everyone,
>
> I'm having some issues with a stored procedure. This is a legacy
> development, so the time was stored in a varchar field and the date
> in
> a timestamp field.
>
> The issue stills happens
Karol,
if you worry about database size after update, i could suggest to split huge
update
by few smaller, each in own transaction and garbage collect between passes.
I.e. something like
update t set ... where id between 0 and N;
commit;
select count(*) from t where id between 0 and N;
commit;
W dniu 2016-04-05 12:45:34 użytkownik Dimitry Sibiryakov s...@ibphoenix.com
[firebird-support] napisał:
> 05.04.2016 12:43, liviuslivius liviusliv...@poczta.onet.pl [firebird-support]
> wrote:
> > but what happens at merge stage (delta merging) when i unlock
05.04.2016 12:43, liviuslivius liviusliv...@poczta.onet.pl [firebird-support]
wrote:
> but what happens at merge stage (delta merging) when i unlock database?
> page will be overriden or new one will be created and old will be marked as
> empty?
Old pages will be overwritten, new ones will
Karol,
if you worry about database size after update, i could suggest to split huge
update
by few smaller, each in own transaction and garbage collect between passes.
I.e. something like
update t set ... where id between 0 and N;
commit;
select count(*) from t where id between 0 and N;
commit;
05.04.2016 10:21, liviuslivius liviusliv...@poczta.onet.pl [firebird-support]
wrote:
> what is the answer for this A or B?
None of them. Full pages are written to delta file, so you'll have database
in exactly
the same state as per scenario 1.
--
WBR, SD.
Hello everyone,
I'm having some issues with a stored procedure. This is a legacy development,
so the time was stored in a varchar field and the date in a timestamp field.
The issue stills happens after the upgrade from 2.1.5 to 2.1.7 on linux open
suse 11.4 x64, classic engine. However, this
Hi,
thanks Tim for warning - i know fragmenting records are bad
but in my case this probably not happen because this is ppmxl database with
numbers only
but do you know what will be answer A or B?
If no one answers I'll have to test yourself ;-)
regards,
Karol Bieniaszewski
If the
If the update makes the records longer (after run-length encoding) it's
even more fun, as you might get fragmentation (of records across pages)
and access times can then increase by a very large factor indeed, even
to the extent of completely crippling the performance of an entire
application.
Hi,
i must update big table 100 GB
and as we know when we do update then new record version will be created.
scenarion 1:
1. Table size 100GB (db size 200GB)
2. Update field in all records generate 100GB new record versions
3. table size after is 200GB (db size 300GB)
4. sweep remove 100GB and
'Andrew Zenz' and...@aimsoftware.com.au [firebird-support] wrote:
> FYI FirstAID scanned the database and identified 2 tables as having
> corruption. I attempted a data pump with DBW excluding those 2 tables
> but it failed on several other tables, tables that FirstAID claims are
> clean.
The
18 matches
Mail list logo