Re: Add exclusive backup deprecation notes to documentation
| От | Magnus Hagander |
|---|---|
| Тема | Re: Add exclusive backup deprecation notes to documentation |
| Дата | |
| Msg-id | CABUevEzzC8RSbR=TBS3fGxkdwRXOos_JsXBw2Q8ECiDg89qLzg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add exclusive backup deprecation notes to documentation (David Steele <david@pgmasters.net>) |
| Ответы |
Re: Add exclusive backup deprecation notes to documentation
|
| Список | pgsql-hackers |
On Fri, Mar 29, 2019 at 1:49 PM David Steele <david@pgmasters.net> wrote:
On 3/29/19 12:46 PM, Robert Haas wrote:
> On Fri, Mar 29, 2019 at 8:45 AM David Steele <david@pgmasters.net> wrote:
>> Are we planning to back-patch this? The deprecation was added to the
>> docs in 9.6 -- I think these clarifications would be helpful.
>
> I wasn't planning too, but I guess we could consider it. I'd be more
> inclined to back-patch the documentation changes than the message text
> changes, but what do other people think?
I think we should definitely do the docs, I'm 50% on the message. You
could argue that is is a behavioral change, but it is pretty important info.
+1 on the docs.
Is the changes to the messages going to cause issues or weirdness for translators? That would be a reason not to backpatch it. Without that, I'm leaning towards backpatching it.
В списке pgsql-hackers по дате отправления: