On 2015-07-29 13:45:22 +0100, Simon Riggs wrote: > So this would be needed when creating a standalone backup that would not be > persistently connected to the master, yet we want to bring it up as a > live/writable server in a single command
I'm not understanding what you mean with 'single command' here. Currently there's no way to do this safely without configuring a high enough wal_keep_segments. You can (since yesterday) manually create a slot, run pg_basebackup, and drop the slot. But that's not safe if your script is interrupted somehow. Since many base backups are run in a non-interactive fashion asking for intervention to clean up in that case imo is not an acceptable answer. > and we want to make it easy to script in case our script is killed? Or the connection dies/is killed, or the server is restarted, or ... -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
