try this and report errors if you find any.
Though, you would want to switch to 9.3 to do such things without a
WAL archive.
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
t the default
value too high."
http://www.postgresql.org/docs/9.3/static/runtime-config-resource.html
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
he database and
> set wal_level=hotstandby and archive_mode=on. After I do that, I notice that
> the WAL sequence number "rewinds" a little bit, overlaping with the old
> ones... Is this normal?
can you show the output of "ls -l " for your pg_xlog?
--
Amit Langote
which
> all WAL segments to apply to bring the backup to a consistent state?
>
By "bringing backup to a consistent state", you mean "restoring from
it to a consistent state", right?
Do you have archiving turned on?
--
Amit Langote
--
Sent via pgsql-admin mailing list (pg
Hello,
Thanks for posting the output as I asked for. I could not immediately
understand what happened so I posted this to pgsql-hackers to let them
have a look at the issue, though I will reply if find anything
interesting.
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin
Hello,
Can you provide the output of following query?
select pg_xlogfile_name(pg_current_xlog_location());
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
latest in your "ls -lrt" output).
By the way, what are the values of following configuration parameters
for your cluster?
checkpoint_segments=?
checkpoint_timeout=?
archive_mode=?
archive_command=?
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To ma
the snapshot containing the backup_label file, use it
for testing, occasionally write to it and then discard the snapshot.
Since the snapshot is copy-on-write, the whole operation seems to
require less storage than otherwise (like a full base backup)
I am also eager to know if anybody has trie
ovide
some pointers as to what is happening.
--
Amit Langote
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
