| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Subject: | Re: PATCH: Exclude additional directories in pg_basebackup |
| Date: | 2016-08-15 21:07:42 |
| Message-ID: | 998e9447-67ef-1d2f-d227-363de456b59e@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/15/16 4:58 PM, Jim Nasby wrote:
> On 8/15/16 2:39 PM, David Steele wrote:
>> That patch got me thinking about what else could be excluded and after
>> some investigation I found the following: pg_notify, pg_serial,
>> pg_snapshots, pg_subtrans. These directories are all cleaned, zeroed,
>> or rebuilt on server start.
>
> If someone wanted to scratch an itch, it would also be useful to put
> things that are zeroed under a single dedicated directory, so that folks
> who wanted to could mount that on a ram drive. It would also be useful
> to do that for stuff that's only reset on crash (to put it on local
> storage as opposed to a SAN).
I definitely have something like that in mind and thought this was a
good place to start.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-08-15 21:11:55 | Re: Let's get rid of the separate minor version numbers for shlibs |
| Previous Message | Jim Nasby | 2016-08-15 20:58:45 | Re: PATCH: Exclude additional directories in pg_basebackup |