| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Don Baccus <dhogaza(at)pacifier(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Priorities for 6.6 |
| Date: | 1999-06-07 00:44:37 |
| Message-ID: | 199906070044.UAA17625@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Oh, I see. SELECT is a transaction, so it flushes pglog. Re-added to
TODO.
> Bruce Momjian wrote:
> >
> > > 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
>
> When selecting (i.e. - read-only) transaction commits,
> it change pg_log - we obviously can avoid this!
> No sense to store commit/abort status of read-only xactions!
>
> Vadim
>
--
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 | Mark Hollomon | 1999-06-07 00:58:49 | Re: [HACKERS] Priorities for 6.6 |
| Previous Message | Jan Wieck | 1999-06-07 00:04:31 | Re: [HACKERS] Priorities for 6.6 |