aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/xlog.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2014-01-02 18:17:29 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2014-01-02 18:17:29 -0300
commit948a3dfbb79a7e63e3bf31253837fa723f36d8c0 (patch)
tree95793ab6bd6c227a2d4058b50950443065d1c292 /src/backend/access/transam/xlog.c
parent03db7945961c449ddd42be883e226bb889270161 (diff)
downloadpostgresql-948a3dfbb79a7e63e3bf31253837fa723f36d8c0.tar.gz
postgresql-948a3dfbb79a7e63e3bf31253837fa723f36d8c0.zip
Handle 5-char filenames in SlruScanDirectory
Original users of slru.c were all producing 4-digit filenames, so that was all that that code was prepared to handle. Changes to multixact.c in the course of commit 0ac5ad5134f made pg_multixact/members create 5-digit filenames once a certain threshold was reached, which SlruScanDirectory wasn't prepared to deal with; in particular, 5-digit-name files were not removed during truncation. Change that routine to make it aware of those files, and have it process them just like any others. Right now, some pg_multixact/members directories will contain a mixture of 4-char and 5-char filenames. A future commit is expected fix things so that each slru.c user declares the correct maximum width for the files it produces, to avoid such unsightly mixtures. Noticed while investigating bug #8673 reported by Serge Negodyuck.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions