| 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-17 05:09:58 |
| Message-ID: | 200111170509.fAH59we27942@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:
> > Seriously, how do OS's handle partial page write, especially to
> > directories?
I realize UPDATE also requires pre-page writes for the old tuples. What
bothers me is that unlike INSERT and UPDATE of new rows, DELETE and
UPDATE of old rows is not writing new data but just setting transaction
ID's. I wish there was a way to store those XID's somewhere else so the
page wouldn't have to be modified.
--
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 | Brent Verner | 2001-11-17 06:31:56 | Re: table names |
| Previous Message | Bruce Momjian | 2001-11-17 05:08:16 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-11-17 05:14:34 | Re: Super Optimizing Postgres |
| Previous Message | Bruce Momjian | 2001-11-17 05:08:16 | Re: TOAST performance (was Re: [GENERAL] Delete Performance) |