| From: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
|---|---|
| To: | Vladimir Borodin <root(at)simply(dot)name> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: pg_rewind to skip config files |
| Date: | 2017-09-07 07:21:21 |
| Message-ID: | CAN-RpxDhc_8JOq=cT9vd6MqWQaS0ZtvSf2LFV1V+bjOoEz02ow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
One more side to this which is relevant to other discussions.
If I am rewinding back to before when a table was created, the current
algorithm as well as any proposed algorithms will delete the reference to
the relfilenode in the catalogs but not the file itself. I don't see how
an undo subsystem would fix this.
Is this a reason to rethink the idea that maybe a pg_fsck utility might be
useful that could be run immediately after a rewind?
--
Best Regards,
Chris Travers
Database Administrator
Tel: +49 162 9037 210 | Skype: einhverfr | www.adjust.com
Saarbrücker Straße 37a, 10405 Berlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-09-07 07:22:17 | Re: Re: [COMMITTERS] pgsql: pg_rewind: Fix some problems when copying files >2GB. |
| Previous Message | Fabien COELHO | 2017-09-07 07:15:05 | Re: pgbench: Skipping the creating primary keys after initialization |