| From: | Shigeru Hanada <hanada(at)metrosystems(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, jagan <jaganrvce(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL, xl_heap_insert and tuple oid mystry |
| Date: | 2011-04-13 02:23:00 |
| Message-ID: | 4DA50904.4000304@metrosystems.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2011/04/13 8:34), Tom Lane wrote:
> Greg Stark<gsstark(at)mit(dot)edu> writes:
>> Doesn't pg_lesslog depend on this?
>
> One hopes not.
AFAIK it's safe because pg_lesslog removes full-page image only when it
has enough information for substitute incremental log.
For example of XLOG_HEAP_INSERT, pg_lesslog generates incremental logs
such as xl_heap_header and tuple image from the inserted tuple in the
full-page image, and replaces full-page image with them.
Regards,
--
Shigeru Hanada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-04-13 06:06:11 | Re: POSIX shared memory redux |
| Previous Message | Tom Lane | 2011-04-13 00:43:43 | Re: WAL, xl_heap_insert and tuple oid mystry |