Re: Why copy_relation_data only use wal whenWALarchiving is enabled

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Why copy_relation_data only use wal whenWALarchiving is enabled
Дата
Msg-id 1192638802.4233.102.camel@ebony.site
обсуждение исходный текст
Ответ на Re: Why copy_relation_data only use wal whenWALarchiving is enabled  (Heikki Linnakangas <heikki@enterprisedb.com>)
Ответы Re: Why copy_relation_data only use wal whenWALarchivingis enabled  (Heikki Linnakangas <heikki@enterprisedb.com>)
Список pgsql-hackers
On Wed, 2007-10-17 at 15:02 +0100, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > If you've got a better problem statement it would be good to get that
> > right first before we discuss solutions.
> 
> Reusing a relfilenode of a deleted relation, before next checkpoint
> following the commit of the deleting transaction, for an operation that
> doesn't WAL log the contents of the new relation, leads to data loss on
> recovery.

OK, thanks. 

I wasn't aware we reused refilenode ids. The code in GetNewOid() doesn't
look deterministic to me, or at least isn't meant to be.
GetNewObjectId() should be cycling around, so although the oid index
scan using SnapshotDirty won't see committed deleted rows that shouldn't
matter for 2^32 oids. So what gives?

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



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

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: rolcanlogin vs. the flat password file
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Why copy_relation_data only use wal whenWALarchivingis enabled