Re: DROP DATABASE vs patch to not remove files right away

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: DROP DATABASE vs patch to not remove files right away
Дата
Msg-id 7765.1208356876@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: DROP DATABASE vs patch to not remove files right away  (Heikki Linnakangas <heikki@enterprisedb.com>)
Ответы Re: DROP DATABASE vs patch to not remove files right away  (Heikki Linnakangas <heikki@enterprisedb.com>)
Список pgsql-hackers
Heikki Linnakangas <heikki@enterprisedb.com> writes:
> Florian suggested a scheme where the xid and epoch is embedded in the 
> filename, but that's unnecessarily complex. We could just make 
> relfilenode a 64-bit integer. 2^64 should be enough for everyone.

Doesn't fix the problem unless DB and TS OIDs become int64 too;
in fact, given that we generate relfilenodes off the OID counter,
it's difficult to see how you do this without making *all* OIDs
64-bit.

Plus you're assuming that the machine has working 64-bit ints.
There's a large difference in my mind between saying "bigint
doesn't work right if you don't have working int64" and "we don't
guarantee the safety of your data if you don't have int64".
I'm not prepared to rip out the non-collision code until such
time as we irrevocably refuse to build on machines without int64.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: count(*) performance improvement ideas
Следующее
От: Joe Conway
Дата:
Сообщение: Re: count(*) performance improvement ideas