diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-08-19 12:33:07 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-08-19 12:56:18 -0400 |
| commit | 78e1220104227c86b4b49d0fc123db7fa596d43d (patch) | |
| tree | 023052b710d2956bb09a6dd45e378e23bbb3806c /src/backend/access/transam/xlog.c | |
| parent | 1bc5935b67c77f27bf653089e757476cfb4245e1 (diff) | |
| download | postgresql-78e1220104227c86b4b49d0fc123db7fa596d43d.tar.gz postgresql-78e1220104227c86b4b49d0fc123db7fa596d43d.zip | |
Fix pg_upgrade failure from servers older than 9.3
When upgrading from servers of versions 9.2 and older, and MultiXactIds
have been used in the old server beyond the first page (that is, 2048
multis or more in the default 8kB-page build), pg_upgrade would set the
next multixact offset to use beyond what has been allocated in the new
cluster. This would cause a failure the first time the new cluster
needs to use this value, because the pg_multixact/offsets/ file wouldn't
exist or wouldn't be large enough. To fix, ensure that the transient
server instances launched by pg_upgrade extend the file as necessary.
Per report from Jesse Denardo in
CANiVXAj4c88YqipsyFQPboqMudnjcNTdB3pqe8ReXqAFQ=HXyA@mail.gmail.com
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions