hi all!
should we add disclaimer in pitr documentation about cp and fsync?
cp does not fsync.
and dd for example can do fsync.
-- misha
hi there!
for me case listed below looks like something goes wrong (at least very strange)
pg 9.2.10
* schema:
base_table ==> inheritance_with_before_trigger ==> child_table ==>
audit_after_trigger ==> child_table_log
* init sql:
create schema tmp;
--create extension hstore;
-- inheritance par
hi!
from master:
pg_xlogfile_name -- right!
from standby:
using replication prtotocol (example from version 92)
psql -h "$host" -F' ' -c 'IDENTIFY_SYSTEM' 'dbname=replication replication=true'
-- misha
>Понедельник, 20 июля 2015, 11:13 +03:00 от Vladimir Borodin :
>
>Hi all.
>
>What is the best
http://multicorn.org/
another cool stuff to generalize interconnections
Wed, 22 Oct 2014 22:34:06 -0700 от Postgres India :
>Thanks a lot Remi, Merlin and Pavel...I will give it a try.
>
>On Wed, Oct 22, 2014 at 6:36 AM, Merlin Moncure < mmonc...@gmail.com > wrote:
>>On Wed, Oct 22, 201
Hello!
Is there any reason why pg_basebackup has limitation in an online backup from
the standby: "The backup history file is not created in the database cluster
backed up."
?
So i can't get last xlog file needed to restore :(
Think i can use -x option for getting last xlog file, but i would l
Hello!
We are experiencing suspicious and very painful case in our
top-business-critical database. We have only 7 weeks before emergency stop of
the cluster cause wraparound task in autovacuum process can not be finished
again and again.
PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled b
Hello, Tom! Thank you for so fast answer.
We did manual vacuum freeze with delay 10 also but unfortunately vacuum did
nothing with pg_class.relfrozenxid too.
Vacuum delay values like 10-40 work very well for many years in our production
cases.
> It's not terribly surprising that it's failing t
