Subject | Re: FB deadlock during big table indexing on Linux |
---|---|
Author | taliyev |
Post date | 2006-04-23T19:35:24Z |
--- In firebird-support@yahoogroups.com, BogusÅaw Brandys
<brandys@...> wrote:
Even though both directories are on the same partition!?!?
Thank you!
<brandys@...> wrote:
>on
> taliyev wrote:
> > --- In firebird-support@yahoogroups.com, Helen Borrie <helebor@>
> > wrote:
> >>
> >>>> At 02:56 AM 23/04/2006, you wrote:
> >>>>> We have huge database ( 30 GB) that seems to be working ok
> >>>>> Windows. We need to port this database to Linux.Transportable
> >>>>> backup file is about 20GB in size. Biggest table is about 185and
> >>>>> millions of records.
> >>
> >>
> >> At 11:56 AM 23/04/2006, you wrote:
> >>> Our Linux is CentOS 4.3 (RedHat Enterprise clone) with ext3
> >>> partition. We have configured /tmp to be used for temp files
> >>> this directory spans across entire disk space. We have about90 GB
> >>> available for it to grow.. FB has `rwx' permissions thereâ¦your
> >>>
> >>> We have also tried to increase SortMemBlockSize and
> >>> SortMemUpperLimit with no success. Any other suggestions?
> >> Not a lot. What data type is the primary key defined as in
> > metadata?and/or
> >> PLEASE DO NOT TOP POST WHEN YOU REPLY TO POSTINGS !!
> >> Edit the existing text and place your reply within the text
> > at the end.are
> >> ./heLen
> >>
> >
> > This particular table does not have PK defined. Indexes we have
> > on VARCHAR(3 or 4) fields and are non-unique, but highselectivity.
> > It seems that FB looses it's handle on temp files⦠I do notknow
> > whyâ¦. Somehow Windows FB version can handle those indexes andLinux
> > cannot...THAT WAS IT! I have relocated temp directory and IT WORKS!
> >
>
> Maybe try to make other directory for temp space and use that for
> testing.If you would restore using that other temp directory then
> probably something is messing with /tmp directory (cron job?)
>
>
> Regards
> Boguslaw
>
Even though both directories are on the same partition!?!?
Thank you!