| От | Mark Kirkwood |
|---|---|
| Тема | Rename a database that has connections |
| Дата | |
| Msg-id | 4ECB1349.30603@catalyst.net.nz обсуждение исходный текст |
| Ответы |
Re: Rename a database that has connections
Re: Rename a database that has connections |
| Список | pgsql-hackers |
I've been helping out several customers recently who all seem to be wrestling with the same issue: wanting to update/refresh non-production databases from the latest corresponding prod version. Typically they have (fairly complex) scripts that at some point attempt to restore a dump into new database and then rename the to-be-retired db out of the way and rename the newly restored one to take over. In many cases such scripts would be simplified if a database could be renamed without requiring its connections terminated. I've been asked several times if this could be added... so I've caved in a done a patch that allows this. The default behavior is unchanged - it is required to specify an additional trailing FORCE keyword to elicit the more brutal behavior. Note that existing connections to the renamed database are unaffected, but obviously SELECT current_database() returns the new name (in the next transaction). regards Mark
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера