From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, dhogaza(at)pacifier(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Priorities for 6.6 |
Date: | 1999-06-06 18:44:49 |
Message-ID: | m10qhub-0003kGC@orion.SAPserv.Hamburg.dsh.de |
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
I think this entry should stay.
In fact, there is a write on every transaction that
commits/aborts even if it's one that doesn't modify any data.
pg_log is written for SELECT only transactions too. I'm
nearly 99.5% sure that not fsync()'ing those transaction
would not hit reliability and we might have to work it out.
This might be one cause that surrounding a bunch of SELECT
statements by BEGIN/END speeds up PostgreSQL in non -F mode.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-06-06 18:47:03 | Re: [HACKERS] Priorities for 6.6 |
Previous Message | Don Baccus | 1999-06-06 18:43:48 | Re: [HACKERS] Priorities for 6.6 |