Re: [HACKERS] Change in "policy" on dump ordering?
От | Stephen Frost |
---|---|
Тема | Re: [HACKERS] Change in "policy" on dump ordering? |
Дата | |
Msg-id | 20170222233710.GR9812@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: [HACKERS] Change in "policy" on dump ordering? (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
Список | pgsql-hackers |
Jim, * Jim Nasby (Jim.Nasby@BlueTreble.com) wrote: > On 2/22/17 12:29 PM, Peter Eisentraut wrote: > >On 2/22/17 10:14, Jim Nasby wrote: > >>CREATE MATERIALIZED VIEW tmv AS SELECT * FROM pg_subscription; > >>SELECT 0 > >> > >>IOW, you can create matviews that depend on any other > >>table/view/matview, but right now if the matview includes certain items > >>it will mysteriously end up empty post-restore. > > > >Yes, by that logic matview refresh should always be last. > > Patches for head attached. > > RLS was the first item added after DO_REFRESH_MATVIEW, which was > added in 9.5. So if we want to treat this as a bug, they'd need to > be patched as well, which is a simple matter of swapping 33 and 34. Can you clarify what misbehavior there is with RLS that would warrent this being a bug..? I did consider where in the dump I thought policies should go, though I may certainly have overlooked something. Thanks! Stephen
В списке pgsql-hackers по дате отправления: