| 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:11:08 |
| Message-ID: | 200111220011.fAM0B8S23813@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:
> > Could we add code to detect a partial write when we recover from one
> > using WAL so we can know if these partial writes are ever
> > happening?
>
> What's your point? It clearly *can* happen during power-failure
> scenarios. All the monitoring in the world won't disprove that.
What bothers me about this is that we have the original page with the
old data. It would be nice if we could write the new page in a
different location, make the new page active and recycle the old page at
some later time.
We are storing the pre-page image in WAL, but it seems like a waste
because we already have a pre-image. It is just that we are overwriting
it.
--
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 | Tom Lane | 2001-11-22 00:16:11 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
| Previous Message | Russ McBride | 2001-11-21 22:54:10 | Re: PG vs MySQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-22 00:16:11 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
| Previous Message | Tom Lane | 2001-11-22 00:05:07 | Re: Taking databases offline |