pgsql-server: Now that xmax and cmin are distinct fields again, we

Поиск
Список
Период
Сортировка
От tgl@svr1.postgresql.org (Tom Lane)
Тема pgsql-server: Now that xmax and cmin are distinct fields again, we
Дата
Msg-id 20040917180956.0415D329D95@svr1.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Дерево обсуждения 
Log Message:
-----------
Now that xmax and cmin are distinct fields again, we should zero xmax when
creating a new tuple.  This is just for debugging sanity, though, since
nothing should be paying any attention to xmax when the HEAP_XMAX_INVALID
bit is set.

Modified Files:
--------------
    pgsql-server/src/backend/access/heap:
        heapam.c (r1.175 -> r1.176)

(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/access/heap/heapam.c.diff?r1=1.175&r2=1.176)

В списке pgsql-committers по дате отправления:

Предыдущее
От: neilc@svr1.postgresql.org (Neil Conway)
Дата:
Сообщение: pgsql-server: Hyperlink a reference to DROP CAST in the CREATE CAST
Следующее
От: tgl@svr1.postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql-server: Hashed LEFT JOIN would miss outer tuples with no inner