Dmitry,

Thanks for clearing up when fb_sort files are being deleted.

We are certainly looking for ways to "Just fix your application", however
with complex logic-intensive applications it's not always that simple.

"change %TEMP%" is just not going to work in any enterprise environment.
You can strong-arm your single-license user into doing this but not the IT
departments of companies with thousands of user.

Thanks,

Alec

On Sun, Jun 3, 2012 at 12:26 PM, Dmitry Kuzmenko <kdv@...> wrote:

> **
>
>
> Hello, Alec!
>
> Sunday, June 3, 2012, 10:17:05 PM, you wrote:
>
> AS> Actually, FB correctly deletes fb_sort file used by a transaction
> after the
> AS> transaction completes.
>
> wrong. sort files being deleted when query that have plan sort fetched
> to EOF, i.e. to the last record. Same happens, for example, when
> group by query sort a huge resultset and result fits in memory.
>
> If sort file left in temp, then application was terminated or failed,
> or computer was powered off or reset.
> Nothing to the transactions.
>
> AS> However, we have a lot of long-running concurrent
> AS> transactions which generate a lot of large fb_sort files.
>
> long-running transactions is a different issue. Just fix your application.
>
> AS> Moreover, when our customer rebuilt indexes they ran out of system
> disk space (since this
> AS> is where %TEMP% points to) and left FB in corrupt state.
>
> change %TEMP%.
>
> --
> Dmitry Kuzmenko, www.ib-aid.com
>
>
>


[Non-text portions of this message have been removed]