[Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Thomas Steinmaurer
Hello, currently investigating nbackup reliability/bugs. CORE-2648 is marked as fixed in 2.1.4 and CORE-3521, which is currently open, seems to like similar (forced writes vs. flushing to disc). How do they differ? Thanks. Regards, Thomas

Re: [Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Vlad Khorsun
> Hello, > > currently investigating nbackup reliability/bugs. CORE-2648 is marked as > fixed in 2.1.4 and CORE-3521, which is currently open, seems to like > similar (forced writes vs. flushing to disc). > > How do they differ? CORE-2648 set FW mode for delta file in the same value as of

Re: [Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Thomas Steinmaurer
Hello Vlad, >> currently investigating nbackup reliability/bugs. CORE-2648 is marked as >> fixed in 2.1.4 and CORE-3521, which is currently open, seems to like >> similar (forced writes vs. flushing to disc). >> >> How do they differ? > > CORE-2648 set FW mode for delta file in the same value

Re: [Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Vlad Khorsun
>> So, before CORE-2648 was fixed, delta file was always opened in FW=OFF >> mode >> despite of database settings. > > So, if the server crashes, we have a problem here? If database setting is FW = ON but (before the fix) delta file is opens with FW = OFF then Firebird crash in stalle

Re: [Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Thomas Steinmaurer
>>> So, before CORE-2648 was fixed, delta file was always opened in >>> FW=OFF mode >>> despite of database settings. >> >> So, if the server crashes, we have a problem here? > > If database setting is FW = ON but (before the fix) delta file is opens > with FW = OFF > then Firebird cra

Re: [Firebird-devel] build problem - gpre - firebird3

2011-07-14 Thread Treeve Jelbert
On Wednesday 13 July 2011 14:07:14 Treeve Jelbert wrote: > I tried building firebird3 on linux - amd64, in order to test boolean > support using svn revision #53289 > > It appears that the makefile tries to link both gpre_meta_boot.o and > gpre/gpre_meta.o when building gpre_boot problem resolved

[Firebird-devel] [FB-Tracker] Created: (CORE-3556) Numeric may be set to more that specidied precision

2011-07-14 Thread Roman Krivykh (JIRA)
Numeric may be set to more that specidied precision --- Key: CORE-3556 URL: http://tracker.firebirdsql.org/browse/CORE-3556 Project: Firebird Core Issue Type: Bug Components: Engine

[Firebird-devel] nbackup during TPC-H database generation (scale: 1GB)

2011-07-14 Thread Thomas Steinmaurer
Hello, I ran a quick test of nbackup with Firebird 2.1.4 Classic 32-bit during a TPC-H database generation with scale 1GB. So, a simulated load (insert into statements by the TPC-H generation thingy) in combination with executing nbackup. A first full backup of the database after ~ 30 sec. aft

Re: [Firebird-devel] nbackup during TPC-H database generation (scale: 1GB)

2011-07-14 Thread Dmitry Kuzmenko
Hello, Thomas! Thursday, July 14, 2011, 6:03:10 PM, you wrote: TS> I ran a quick test of nbackup with Firebird 2.1.4 Classic 32-bit during TS> The next TS> level 1 backup hangs now, the delta file fills up and any other database TS> attachments to the database hang as well, so no additional datab

Re: [Firebird-devel] nbackup during TPC-H database generation(scale: 1GB)

2011-07-14 Thread Paul Beach
TS> I ran a quick test of nbackup with Firebird 2.1.4 Classic 32-bit during TS> The next TS> level 1 backup hangs now, the delta file fills up and any other database TS> attachments to the database hang as well, so no additional database TS> attachments possible. > 2.1.4 is old, use higher version

[Firebird-devel] Comments for function parameters

2011-07-14 Thread Dmitry Yemanov
All, I've faced problems while adding into trunk. For procedure parameters, the syntax is: COMMENT ON PARAMETER . IS However, procedures and functions have different namespaces, so there may be a function and its input parameter with exactly the same names. Thus this syntax doesn't look sui

Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Dmitry Yemanov
I'm now convincing myself to the third option: > Extend the syntax but preserve backward compatibility via default: > > COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ... but if the object type specifier is omitted, then the engine tries to be smart and determine whether it's a procedure or a fun

Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Dimitry Sibiryakov
14.07.2011 18:33, Dmitry Yemanov wrote: > I'm now convincing myself to the third option: For me this option looks better than previous two. -- SY, SD. -- AppSumo Presents a FREE Video for the SourceForge Community

Re: [Firebird-devel] nbackup during TPC-H database generation (scale: 1GB)

2011-07-14 Thread Thomas Steinmaurer
> Thursday, July 14, 2011, 6:03:10 PM, you wrote: > > TS> I ran a quick test of nbackup with Firebird 2.1.4 Classic 32-bit during > TS> The next > TS> level 1 backup hangs now, the delta file fills up and any other database > TS> attachments to the database hang as well, so no additional databa

Re: [Firebird-devel] Comments for function parameters

2011-07-14 Thread Paul Vinkenoog
Dmitry wrote: > > Extend the syntax but preserve backward compatibility via default: > > > > COMMENT ON [{PROCEDURE | FUNCTION}] PARAMETER ... > > but if the object type specifier is omitted, then the engine tries to be > smart and determine whether it's a procedure or a function at runtime > (by

Re: [Firebird-devel] nbackup: CORE-3521 and CORE-2648

2011-07-14 Thread Vlad Khorsun
Before CORE-3521 was fixed delta file contents was not flushed to disk when transactions finished. >>> >>> So, without a fix for CORE-3521, cached dirty pages aren't written to >>> disk while nbackup is running at all? >> >> If FW = ON, then this bug should have no impact. > > FW =