Count command too slow
--
Key: CORE-3666
URL: http://tracker.firebirdsql.org/browse/CORE-3666
Project: Firebird Core
Issue Type: Bug
Environment: Win2003 r2 sp2, firebird 2.5.1,cpu Xeon E5620 * 4 ,ram 4G
17.11.2011 11:26, Alex Peshkoff wrote:
> And one more interesting line:
> open("./fb_init", O_RDWR|O_CREAT|O_LARGEFILE, 0600) = 7
> Why is _SHARED_ file opened in CWD? It should go to /tmp/firebird.
Because he explicitly sets FIREBIRD_LOCK to CWD before running ISQL :-)
Dmitry
On 11/17/11 00:38, Damyan Ivanov wrote:
>> Is user, running that script, a member of group firebird?
> No and I can't make it. I am a mere user on the porter machines :)
>
That's a pity and can be even a reason not to deliver ASTs between
processes. On the other hand we have 2 processes started b
Paul,
> On Wednesday 16 November 2011 at 06:04 Dmitry Yemanov wrote:
>
> > Also, some
> > Windows versions are suspected in giving the file system cache too
> > high priority thus possibly swapping out the pages of the process
> > working set, so a largish internal page cache could prove itself t
-=| Alex Peshkoff, 16.11.2011 10:28:52 +0400 |=-
> In standard install procedure empty, firebird group writable file
> firebird.log is created. Does .deb package create that file too?
Yes:
$ ls -l /var/log/firebird2.5.log
-rw-rw 1 firebird firebird 0 Nov 13 18:48 /var/log/firebird2.5.log
> I
ISQL commits changes rather rollback them when Ctrl-C is pressed (on Windows)
--
Key: CORE-3664
URL: http://tracker.firebirdsql.org/browse/CORE-3664
Project: Firebird Core
ISQL does not allow to quit on Ctrl-C under LINUX after establishing successful
connection to database
--
Key: CORE-3665
URL: http://tracker.firebirdsql.org/browse
Adriano dos Santos Fernandes [2011-11-13 02:34] :
> Barriers are supposed to act on file's metadata only, but the speedy
> problem we see don't make that appear to be true.
;)
we are not alone in this case, same for PG for example
http://blog.dryft.net/2011/04/effects-of-filesystems-and-mount.html
Hello, Dmitry!
Wednesday, November 16, 2011, 9:04:18 AM, you wrote:
DY> Handling memory allocation automagically may sound like a clever idea,
DY> but let's don't forget that DBAs often have to set up the higher limit
DY> of the resource consumption, so the cache limit is still likely to
DY> per
