Re: pg15b2: large objects lost on upgrade
От | Robert Haas |
---|---|
Тема | Re: pg15b2: large objects lost on upgrade |
Дата | |
Msg-id | CA+TgmoZtAeh0Si0HxD0NxCqb2u99aURvCXVPyqyqD2O-0tScBQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg15b2: large objects lost on upgrade (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: pg15b2: large objects lost on upgrade
|
Список | pgsql-hackers |
On Thu, Jul 7, 2022 at 4:16 PM Bruce Momjian <bruce@momjian.us> wrote: > You are right to be concerned since you are spanning number spaces, but > I think you are fine because the relfilenode in the user-space cannot > have been used since it already was being used in each database. It is > true we never had a per-database rename like this before. Thanks for checking over the reasoning, and the kind words in general. I just committed Justin's fix for the bug, without fixing the fact that the new cluster's original pg_largeobject files will be left orphaned afterward. That's a relatively minor problem by comparison, and it seemed best to me not to wait too long to get the main issue addressed. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: