Florian Weimer writes:
> It's still quite surprising that this temporarily needs multiple
> gigabytes of RAM, much more than what's required in in terms of work_mem
> to make this query run quickly.
I doubt there's anything all that interesting there, but if you want
people to investigate this
On 01/22/2014 06:56 PM, Tom Lane wrote:
Florian Weimer writes:
I've got a query which causes PostgreSQL to create hundreds of thousands
of temporary files, many of them empty. The process also needs a lot of
memory. I suspect this is due to bookkeeping for those files.
The query looks like
On Wed, Jan 22, 2014 at 6:59 PM, Florian Weimer wrote:
> This happens with postgresql-server-9.3.2-2.fc20.x86_64.
>
> I track this down to a lower-than-usual setting of work_mem, to 1MB, after
> the upgrade to 9.3.
>
> With work_mem set to 8MB, the query completes in a reasonable time frame,
> wit
Florian Weimer writes:
> I've got a query which causes PostgreSQL to create hundreds of thousands
> of temporary files, many of them empty. The process also needs a lot of
> memory. I suspect this is due to bookkeeping for those files.
> The query looks like this:
> [ huge hash join ]
> I tr
I've got a query which causes PostgreSQL to create hundreds of thousands
of temporary files, many of them empty. The process also needs a lot of
memory. I suspect this is due to bookkeeping for those files.
The query looks like this:
SELECT ef.arch::text, en.name, file_id, f.name
FROM symb
