Re: Suggestions for the best strategy to emulate returning multiple sets of results - Mailing list pgsql-general

From Jasen Betts
Subject Re: Suggestions for the best strategy to emulate returning multiple sets of results
Date
Msg-id k5dgia$2vh$1@reversiblemaps.ath.cx
Whole thread Raw
In response to Suggestions for the best strategy to emulate returning multiple sets of results  (Seref Arikan <serefarikan@kurumsalteknoloji.com>)
Responses Re: Re: Suggestions for the best strategy to emulate returning multiple sets of results  (Seref Arikan <serefarikan@gmail.com>)
List pgsql-general
On 2012-10-10, Seref Arikan <serefarikan@kurumsalteknoloji.com> wrote:
> --f46d0443048225e0e704cbb5e0ee
> Content-Type: text/plain; charset=ISO-8859-1
>
> Thanks Bret,
> I'm concerned about what happens when my functions under high load fills
> the ramdrive with temporary tables I'm using. The advantage of telling
> postgres to use ram with an option to fall back to disk is significantly
> better in terms of uptime.
> However, I was thinking about some mechanism in the middle tier that
> watches the space in the ram drive and redirects queries to functions that
> create temp tables on disk, if ram drive is close to full. That may help me
> accomplish what I'm trying to

That's what operating systems are for,  ramdisk is only ever a hint,
is ram is short it will wind up in swap, if ram is plentiful a disk
table will be fully buffered in ram.

--
⚂⚃ 100% natural

pgsql-general by date:

Previous
From: Jasen Betts
Date:
Subject: Re: moving from MySQL to pgsql
Next
From: Jasen Betts
Date:
Subject: Re: Postgres DB Migration from 8.3 to 9.1