Re: Change in "policy" on dump ordering?
Michael Banck <michael.banck@credativ.de>
From: Michael Banck <michael.banck@credativ.de>
To: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com>, Jim Nasby <Jim.Nasby@bluetreble.com>,
Kevin Grittner <kgrittn@gmail.com>, Jordan Gigov <coladict@gmail.com>, Pg
Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-03T10:44:35Z
Lists: pgsql-hackers
Am Donnerstag, den 27.07.2017, 15:52 -0400 schrieb Tom Lane: > So I'm thinking we should consider the multi-pass patch I posted as > a short-term, backpatchable workaround, which we could hope to > replace with dependency logic later. +1, it would be really nice if this could be fixed in the back-branches before v11. Michael -- Michael Banck Projektleiter / Senior Berater Tel.: +49 2166 9901-171 Fax: +49 2166 9901-100 Email: michael.banck@credativ.de credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
Commits
-
Fix pg_dump/pg_restore to emit REFRESH MATERIALIZED VIEW commands last.
- b93217653b68 9.4.13 landed
- 65048cf23dba 9.5.8 landed
- 3d76328298ca 9.6.4 landed
- 3eb9a5e7c4c9 10.0 landed
- 035bb82222bc 9.3.18 landed