From: | constzl <const_sunny(at)126(dot)com> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | ran out of space in relation map |
Date: | 2019-08-24 03:48:09 |
Message-ID: | 73af4845.12a1.16cc1bd1151.Coremail.const_sunny@126.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi All:
Look at the following code.
"The map file should be kept to no more than one standard-size disk sector (ie 512 bytes)"
This means that the number of mapping objects can not be more than MAX_MAPPINGS, which is 62 now.
If one day in the future, it does need to be more than 62, then what to do?
In fact, I had such a problem. After I add some shared catalog relation (and its toast relation,index), the error
"ran out of space in relation map" occurs when initdb.
After debugging, it is found that the number of shared objects is indeed more than 62, and of course, its size is
more than 512 bytes.
Can someone help me? Thanks!
Best Regards
const.zl
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-08-24 05:58:22 | Re: ran out of space in relation map |
Previous Message | Merlin Moncure | 2019-08-24 03:02:03 | Re: data modifying WITH seems to drop rows in cascading updates -- bug? |