Postgresql – Slony not replicating changes from a dump file

I suspect you are going to have to disable application access during the uninstall process. The basic problem is that Slony uses large numbers of triggers to maintain the binary logs for shipping. These triggers are going to be hard to delete while there is concurrent access.

I use pgAdmin 1.14.2 on Ubuntu, but I imagine this will work anywhere else as well.

In pgAdmin, go to Tools -> Backup..., where you'll get a dialog with a few tabs. On the first one (File Options) give a filename and choose the 'Plain' format from the dropdown list. On the next tab (Dump Options #1) tick the 'Use Insert commands' option at the bottom and the 'Only data' option at the top (and don't tick the 'Use Column Inserts' one). On the Objects tab you can choose whichever tables you need then press the Done button.

Now you'll get a file with the INSERT statements for every row - and some other commands as well. You can remove the latter with your favourite editor. Then the list can be sorted - if you want to sort by the first column in the table (that is, more often than not the ID) then you can use a simple sort. If you need a different sorting then you have to apply some magic in an editor.