Re: Detecting corrupted pages earlier
От | Peter Eisentraut |
---|---|
Тема | Re: Detecting corrupted pages earlier |
Дата | |
Msg-id | Pine.LNX.4.44.0304031941210.2215-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: Detecting corrupted pages earlier (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Detecting corrupted pages earlier
|
Список | pgsql-hackers |
Tom Lane writes: > Andrew Sullivan expressed concern about this, too. The thing could > be made a little more failsafe if we made it impossible to set > ZERO_DAMAGED_PAGES to true in postgresql.conf, or by any means other > than an actual SET command --- whose impact would then be limited to > the current session. This is kind of an ugly wart on the GUC mechanism, > but I think not difficult to do with an assign_hook (it just has to > refuse non-interactive settings). Fighting against people who randomly change settings without being informed about what they do is pointless. It's like trying to prevent 'rm -rf /*'. And it's not like you can easily set anything in postgresql.conf by accident. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: