| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, julyanto SUTANDANG <julyanto(at)equnix(dot)co(dot)id>, Dinesh Chandra 12108 <Dinesh(dot)Chandra(at)cyient(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Backup taking long time !!! |
| Date: | 2017-01-23 17:43:56 |
| Message-ID: | CANP8+jLGMPN=8gT5sqntMJwMKZps=o3WAQeLVd8dqNqPCkXyUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 23 January 2017 at 17:12, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> Just to make sure anyone reading the mailing list archives isn't
>> confused, running pg_start_backup does *not* make PG stop writing to
>> BASEDIR (or DATADIR, or anything, really). PG *will* continue to write
>> data into BASEDIR after pg_start_backup has been called.
>
>
>
> Correct. Unfortunately it is a very common myth that it does cause
> PostgreSQL to stop writing to the base dir.
Never heard that one before. Wow. Who's been saying that?
It's taken me years to hunt down all invalid backup memes and terminate them.
Never fails to surprise me how many people don't read the docs.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-23 17:47:37 | Re: Backup taking long time !!! |
| Previous Message | Jeff Janes | 2017-01-23 17:32:28 | Re: Backup taking long time !!! |