| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>, "Russell Smith" <mr-russ(at)pws(dot)com(dot)au>, "Jan Wieck" <JanWieck(at)yahoo(dot)com> |
| Subject: | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
| Date: | 2010-06-04 17:56:54 |
| Message-ID: | 4C08F8160200002500031FCC@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> If we were actually going in this direction we'd want to write a
> much better WAL-text-dump tool than we have, and then in principle
> somebody could sanitize the text output before shipping it off.
I wouldn't think this would be practical unless there was a way to
scan the WAL files and dump only the bits related to the affected
pages, and probably with at least an option (possibly default) to
just mention the data type and length, rather than showing the
actual values -- how often are the values relevant, anyway? (Not
rhetorical; I really don't know.)
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-06-04 17:57:58 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |
| Previous Message | Kevin Grittner | 2010-06-04 17:52:50 | Re: Idea for getting rid of VACUUM FREEZE on cold pages |