From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "P(dot)J(dot) \"Josh\" Rovero" <rovero(at)sonalysts(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
Date: | 2001-11-22 00:49:14 |
Message-ID: | 200111220049.fAM0nEJ25553@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> I don't see how that reduces the total amount of disk traffic?
>
> > Well, right now we write the pre-image to WAL, then write the new page
> > over the old one. In my case, you just write the new, and somewhere
> > record that the old page is no longer active.
>
> The devil is in the details of that last little bit. How is "mark a
> page inactive" cheaper than "mark a tuple dead"? More specifically,
> how do you propose to avoid WAL-logging the page you are going to do
> this marking in? Seems you still end up with a WAL page image for
> something.
I was thinking of just throwing the inactive page number into WAL. Much
smaller than the entire page image. You don't touch the page. Does
that help?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(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 | Martijn van Oosterhout | 2001-11-22 01:21:12 | Re: Determining which index to create |
Previous Message | Tom Lane | 2001-11-22 00:37:26 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
From | Date | Subject | |
---|---|---|---|
Next Message | Guy Fraser | 2001-11-22 01:11:48 | Re: postgresql.conf (Proposed settings) |
Previous Message | Tom Lane | 2001-11-22 00:37:26 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |