Re: GIN logging GIN_SEGMENT_UNMODIFIED actions?
| От | Alexander Korotkov |
|---|---|
| Тема | Re: GIN logging GIN_SEGMENT_UNMODIFIED actions? |
| Дата | |
| Msg-id | CAPpHfds5_ayQpmt0Z5qX7K2M6qT7LGD3A7xZzO8YhHFHxzAYdQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | GIN logging GIN_SEGMENT_UNMODIFIED actions? (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: GIN logging GIN_SEGMENT_UNMODIFIED actions?
|
| Список | pgsql-hackers |
trying to debug something I saw the following in pg_xlogdump output:
rmgr: Gin len (rec/tot): 0/ 274, tx: 0, lsn: 1C/DF28AEB0, prev 1C/DF289858, desc: VACUUM_DATA_LEAF_PAGE 3 segments: 5 unknown action 0 ???, blkref #0: rel 1663/16384/16435 blk 310982
note the "segments: 5 unknown action 0 ???" bit. That doesn't seem
right, given:
#define GIN_SEGMENT_UNMODIFIED 0 /* no action (not used in WAL records) */
I've checked GIN code. Have no idea of how such wal record could be generated...
The only idea I have is to add check that we're inserting valid WAL record immediately before XLogInsert().
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
В списке pgsql-hackers по дате отправления: