| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, 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:49:43 |
| Message-ID: | 20170123174943.GL18360@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
* Simon Riggs (simon(at)2ndquadrant(dot)com) wrote:
> 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?
Well, this conversation started because of such a comment, so at least
one person on this thread (though I believe that's been clarified
sufficiently now).
> It's taken me years to hunt down all invalid backup memes and terminate them.
A never-ending and thankless task, so, my thanks to you for your
efforts. :)
> Never fails to surprise me how many people don't read the docs.
+1MM.
Thanks again!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | julyanto SUTANDANG | 2017-01-24 00:08:21 | Re: Backup taking long time !!! |
| Previous Message | Stephen Frost | 2017-01-23 17:47:37 | Re: Backup taking long time !!! |