Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall |
Дата | |
Msg-id | 20180123154537.GA15525@momjian.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Refactor handling of database attributes between pg_dump and pg_dumpall (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Refactor handling of database attributes between pg_dump and pg_dumpall
|
Список | pgsql-hackers |
On Sun, Jan 21, 2018 at 11:02:29AM -0500, Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > On Fri, Jan 19, 2018 at 02:54:25PM -0500, Tom Lane wrote: > >> Command was: DROP DATABASE "template1"; > > > Uh, the oid of the template1 database is 1, and I assume we would want > > to preserve that too. > > I don't feel any huge attachment to that. In the first place, under > this proposal recreating template1 is something you would only need to do > if you weren't satisfied with its default properties as set by initdb. > Which ought to be a minority of users. In the second place, if you are > changing those properties from the way initdb set it up, it's not really > virgin template1 anymore, so why shouldn't it have a new OID? Oh, I see what you mean. I was just worried that some code might expect template1 to always have an oid of 1, but we can just call that code broken. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
В списке pgsql-hackers по дате отправления: