<div><div dir="rtl"><div><br>
<div style="direction: ltr;">I think you miss understood me.</div>
<div style="direction: ltr;">pg_dump dumps the data. the tables, functions and the data saved in them.</div>
<div style="direction: ltr;">I have daily backups for this so i'm not worried.</div>
<div style="direction: ltr;"> </div>
<div style="direction: ltr;">What i'm woried about are the "executables files". These files are what is actualy being updated when you update the version.</div>
<div style="direction: ltr;">I want to be able to roll them back in case of upgrade failure <u>without rolling back the data</u>.</div>
<div style="direction: ltr;"> </div>
<div style="direction: ltr;"> </div>
<div style="direction: ltr;">Basicly what I want is to save on the side all the files that will be change by the update and in case of failure just to replace them back.</div>
<div style="direction: ltr;">Is it doable? How?</div>
</div></div><section class="cust_msg_end"></section><blockquote style="margin:0;margin-bottom:20px;border-top:1px solid #e0e0e0;"><br>ב מאי 10, 2017 16:27, Adrian Klaver כתב:<blockquote style="margin:0;margin-bottom:20px;border-top:1px solid #e0e0e0">On 05/10/2017 06:08 AM, Ron Ben wrote:<br>> I'm about to upgrade my postgresql to the latest 9.3 version<br>> On my test server eveything works.<br>> However I want to save a backup of my production server before the <br>> upgrade...<br>> I'm not sure how I do that.<br><br><a href="https://www.postgresql.org/docs/9.3/static/app-pg-dumpall.html">https://www.postgresql.org/docs/9.3/static/app-pg-dumpall.html</a><br><br>> It says that only system files are changed during upgrade... which <br>> folders exactly I need to save on the side for roll back?<br><br>I would say that would depend on the nature of the release changes.<br><br>> I know I can take a snap shoot of my server before the update but i'm <br>> affried that rolling back to this snap shoot will also roll back the <br>> data itself?<br>> Since after the update the users continue to work I don't want to lose <br>> thier data.<br><br>Well if the upgrade takes then you don't need to rollback. If it did not <br>then the users did not get any work done or any data they entered would <br>be considered suspect. If you are concerned then take another pg_dumpall <br>before rolling back.<br><br><br>> How do I do that?<br><br><br>-- <br>Adrian Klaver<br>adrian(dot)klaver(at)aklaver(dot)com<br><br><br>-- <br>Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)<br>To make changes to your subscription:<br><a href="http://www.postgresql.org/mailpref/pgsql-general">http://www.postgresql.org/mailpref/pgsql-general</a><br><br><br></blockquote></blockquote><br></div>