It looks that you are missing something. Similarly to what you did, here is
an example of PITR using a base backup:
1) Here is my master node doing some archiving:
$ psql -c 'show archive_command' -p 5432
archive_command
On Thu, Aug 8, 2013 at 2:39 PM, Tom Lane wrote:
> h...@tbz-pariv.de writes:
>> For easier deployment it would be nice to have an include_dir directive in
>> pg_hba.conf.
>
> This doesn't seem like a remarkably good idea from here, mainly because
> entries in pg_hba.conf are critically order-depend
Hello
2013/8/11 Petr Chmelar :
> Hi,
>
> according to the previous thread, can you update the documentation, please:
> http://www.postgresql.org/docs/current/static/functions-math.html
> so there is clean what results do you get eg. on "NULL + 1" (and "1 +
> NULL"), which gives you null and it is
Thanks so much.
On 12 Aug 2013, at 6:45 AM, Michael Paquier wrote:
> On Mon, Aug 12, 2013 at 1:53 AM, ascot.m...@gmail.com
> wrote:
>> I want to enable WAL archive on the replica, I am advised that WAL archive
>> can only be enabled on the Master, can you please advise if this is a bug
>> and a
The latest update on original bug report at Red Hat bugzilla shows that the
reproducer is just disable the peer access for 'postgres' user in
pg_hba.conf. So — the old server was most probably still running for OP
(not shut down properly as was originally said).
But basically, this fix is relevan
Hi,
I have tried following test cases about PITR:
a) Time and events on Master :
16:32:03 HKTBegin; CREATE TABLE test22 (id INTEGER PRIMARY KEY);
INSERT INTO test22 VALUES (generate_series(1,22)); End; Commit;
16:35:02 HKTBegin; CREATE TABLE test23 (id INTEGER
