<div dir="ltr"><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, May 7, 2013 at 10:02 AM, Dimitri
Fontaine<span dir="ltr"><<a href="mailto:dimitri@2ndquadrant.fr"
target="_blank">dimitri@2ndquadrant.fr</a>></span>wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px#ccc solid;padding-left:1ex"><div id=":6q5">Rather than take some locks, you can now prevent the
databaseobjects<br /> from changing with an event trigger. pg_dump could install that event<br /> trigger in a
preparingtransaction, then do its work as currently, then<br /> when done either remove or disable the event
trigger.<br/><br /> All the event trigger has to do is unconditionnaly raise an exception<br /> with a message
explainingthat no DDL command is accepted during when a<br /> dump is in progress.</div></blockquote></div><br /><br
/></div><divclass="gmail_extra">I'm thinking of a case where a hot standby is executing a pg_dump and DDL is issued on
themaster -- would that cause any unexpected problems on the hot standby?<br /></div></div>
