| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Don Baccus <dhogaza(at)pacifier(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Priorities for 6.6 |
| Date: | 1999-06-05 18:14:58 |
| Message-ID: | 199906051814.OAA20833@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> In short, if you load a bunch of tuples into a table, the first select
> after the load can run a lot slower than you might expect, because it'll
> be writing back most or all of the pages it touches. But that penalty
> doesn't affect every select, only the first one to scan a newly-written
> tuple.
I have removed this from the TODO list:
* Prevent fsync in SELECT-only queries
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-06-05 18:25:20 | Re: [HACKERS] Priorities for 6.6 |
| Previous Message | Don Baccus | 1999-06-05 17:10:07 | Re: [HACKERS] Priorities for 6.6 |