| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Hans-Jürgen Schönig <hs(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Threaded Sorting |
| Date: | 2002-10-04 18:54:24 |
| Message-ID: | 25610.1033757664@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Bingo! Want to increase sorting performance, give it more I/O
> bandwidth, and it will take 1/100th of the time to do threading.
> Added to TODO:
> * Allow sorting to use multiple work directories
Yeah, I like that. Actually it should apply to all temp files not only
sorting.
A crude hack would be to allow there to be multiple pg_temp_NNN/
subdirectories (read symlinks) in a database, and then the code would
automatically switch among these.
Probably a cleaner idea would be to somehow integrate this with
tablespace management --- if you could mark some tablespaces as intended
for temp stuff, the system could round-robin among those as it creates
temp files and/or temp tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Copeland | 2002-10-04 19:00:53 | Re: Threaded Sorting |
| Previous Message | Zeugswetter Andreas SB SD | 2002-10-04 18:50:33 | Re: Return of INSTEAD rules |