Rafael Martinez writes:
> Tom Lane wrote:
>> I think this is normal behavior now, if you have an unloaded server.
>> pg_start_backup now forces a segment switch, so if nothing much else is
>> happening it's quite likely that the recorded start point will be the
>> beginning of the WAL segment (plu
Tom Lane wrote:
> Rafael Martinez writes:
>
>> All PITR backup history files created when running a PITR base backup on
>> all PostgreSQL clusters running in this new server (at different hours
>> during the night) got an identical 2nd part file name.
>
>> <24 digits>.0020.backup e.g.00
Rafael Martinez writes:
> After upgrading to 8.3.9 and moving some our PostgreSQL clusters to a
> new server yesterday, we have experienced a strange thing this past night.
> All PITR backup history files created when running a PITR base backup on
> all PostgreSQL clusters running in this new ser
Hello
After upgrading to 8.3.9 and moving some our PostgreSQL clusters to a
new server yesterday, we have experienced a strange thing this past night.
All PITR backup history files created when running a PITR base backup on
all PostgreSQL clusters running in this new server (at different hours
du
