Re: WAL, xl_heap_insert and tuple oid mystry
От | jagan |
---|---|
Тема | Re: WAL, xl_heap_insert and tuple oid mystry |
Дата | |
Msg-id | 790093.18811.qm@web32107.mail.mud.yahoo.com обсуждение исходный текст |
Ответ на | Re: WAL, xl_heap_insert and tuple oid mystry (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: WAL, xl_heap_insert and tuple oid mystry
|
Список | pgsql-hackers |
Hi, >> Where is the OID of tuple stored in a WAL record of a >> tuple? If not with xl_heap_header, where is it stored? Is it >> stored at all? > It's stored in the "tuple data" portion. Is the OID also recorded with xl_heap_delete record as well or just the xl_heaptid? From my reading of the code it is notrecorded. In general, why is OID of a tuple relegated as just another tuple data, when it can replace xl_heaptid as a much more stabletuple identifier. I understand that by recording tuples in terms of xl_heaptid (i.e., page/offset) means that the dbcan recover quickly but isn't there some value to storing a much "higher level" information in the WAL logs? For example,tuple manipulations, if recorded in terms of manipulation on tuple oids, can support applications such as these: http://blogs.enterprisedb.com/2011/03/03/more-musings-on-logical-replication/ Just a thought. Thanks, Jagan
В списке pgsql-hackers по дате отправления: