title: Publishing flow in Postgres similar to SSDT
body: <p>I am coming from MSSQL background to the Postgres which I am new to.</p>
  
  <p>In MSSQL we have SSDT for VS which  is a great way of publishing whole scripted DB to the server - and what more importantly is that the update scripts are created automatically for the changes (of course there are cases where they need to be altered but mostly does the work).</p>
  
  <p>So the question is how would a similar flow work with postgres ? </p>
  
  <p>There is one approach to use pg-migration but it requires tedious manual work of writing the bversion migration scripts which is not really the same.</p>
  
  <p>So the feeling I have now is that it is like back on the beginning of 2K to write manually the update scrip for every deployment and to keep it in source control file diffs, very old school.</p>
  
  <p>Any suggestion would be great from the postgres folks out there</p>