Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dividing WAL segments by directories #234

Open
stratumO opened this issue Jun 30, 2020 · 3 comments · May be fixed by #450
Open

Dividing WAL segments by directories #234

stratumO opened this issue Jun 30, 2020 · 3 comments · May be fixed by #450
Assignees

Comments

@stratumO
Copy link

Hi! I suggest dividing WALs from the archive into different directories, because when writing a large number of segments to the network directory (30-40 thousand per day, NFS for example) for several weeks, there are problems with the availability of the directory.

You can divide by dates hours or segment names (for example, as in barman)
Thanks!

@gsmolk
Copy link
Contributor

gsmolk commented Jun 30, 2020

Hello!
Looks like a must have feature and, since we must be able to determine the segment location for WAL parsing, the barman way of grouping them per log segment (one directory for 256 segments) is a good way to do it.
Thank you for the feedback!

@gsmolk gsmolk added this to the 2.5.0 milestone Jun 30, 2020
@beremour
Copy link

I'am usin NFS storage also. It's good to have something like /backup/instance/wal/YY-MM-DD/ subdirs

@gsmolk gsmolk self-assigned this Oct 29, 2020
@gsmolk gsmolk modified the milestones: 2.5.0, 2.6.0 Jun 17, 2021
@kulaginm kulaginm linked a pull request Jan 8, 2022 that will close this issue
@Burus Burus modified the milestones: 2.6.0, 2.5.7 Jul 29, 2022
@Burus
Copy link
Contributor

Burus commented Jul 29, 2022

Hi! We prepare this enhancement in the 2.5.7 release #500

@Burus Burus removed this from the 2.5.7 milestone Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants