Re: how to cancel a query in progress
От | Whit Armstrong |
---|---|
Тема | Re: how to cancel a query in progress |
Дата | |
Msg-id | 8ec76080906171116s56532b36ybd196c2ee0da3c92@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: how to cancel a query in progress (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: how to cancel a query in progress
|
Список | pgsql-general |
Thanks. That's a relief. getting a few "page xxx is uninitialized --- fixing" warnings in the vacuum output, but seems like this should be expected since I killed an insert in progress. can anyone confirm that these warnings are ok? WARNING: relation "balances_primary" page 1883404 is uninitialized --- fixing WARNING: relation "balances_primary" page 1883405 is uninitialized --- fixing WARNING: relation "balances_primary" page 1883406 is uninitialized --- fixing -Whit On Wed, Jun 17, 2009 at 12:09 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote: > Whit Armstrong <armstrong.whit@gmail.com> writes: >> Are there any integrity checks I need to run on the db after this type >> of crash and recovery, or is vacuum --all good enough? > > There isn't anything you need to do. Postgres crashes don't corrupt > on-disk data, as a general rule, and a SIGKILL crash seems particularly > safe from that. > > regards, tom lane >
В списке pgsql-general по дате отправления: