summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.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
commit638cf09e76d70dd83d8123e7079be6c0532102d2 (patch)
tree3f0b173a1e2d7708d462d7899816c7e53b8eceaf /src/backend/access/gist/gist.c
parenta50d97625497b76e3dc7c4aa22cd2c70317ec54d (diff)
downloadpostgresql-638cf09e76d70dd83d8123e7079be6c0532102d2.tar.gz
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/gist/gist.c')
0 files changed, 0 insertions, 0 deletions