We are working on tracking those queries down, but fixing them will require
an upgrade which the customer does not want to do. Moreover, their db size
is 12GB, so it may not be possible to optimize the queries a lot further.

The customer also ran out of disk space trying to rebuild database indexes
which left firebird in a corrupted state. We had to add more space and run
gfix to repair it. This is a different problem, but it's also related to FB
disk usage.

Is TempDirectories setting expected to work in embedded mode? What happens
when max allowed temp space is not big enough for a sort?

Thanks,

Alec

On Fri, Jun 1, 2012 at 12:16 PM, Michael Ludwig <milu71@...> wrote:

> **
>
>
> Alec Swan schrieb am 01.06.2012 um 11:55 (-0600):
>
> > Our customers complain that Firebird creates 6GB temporary sort file
> > and we need to address this asap. Can anyone suggest a solution?
>
> That does sound unhealthy. Have you figured out what query or queries
> are causing these exorbitant temporary sort files? There might be ways
> of tailoring them such that the sort needed to produce the result is
> reduced to a more manageable size.
>
> Michael
>
>
>


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