Re: [GENERAL] pg_upgrade problem

Hi,

Worked a bit to get the ltree problem down to smallest possible, repeatable, situation.

Initial setup:

1. PostgreSQL 8.3.11, configured with:
./configure \
--prefix=/opt/pgsql-8.3.11-int \
--disable-rpath \
--without-perl \
--without-python \
--without-tcl \
--without-openssl \
--without-pam \
--without-krb5 \
--without-gssapi \
--enable-nls \
--enable-integer-datetimes \
--enable-thread-safety \
--with-libxml \
--with-libxslt \
--without-ldap
Built and installed with contrib modules.

2. PostgreSQL 9.0.5 (pre), from git checkout, head of 9.0 branch. Configured with:
./configure \
--prefix=/opt/pgsql-9.0.5a-int \
--enable-debug \
--enable-cassert \
--disable-rpath \
--without-perl \
--without-python \
--without-tcl \
--without-openssl \
--without-pam \
--without-krb5 \
--without-gssapi \
--enable-nls \
--enable-integer-datetimes \
--enable-thread-safety \
--with-libxml \
--with-libxslt \
--without-ldap

Now with these two in place, I can make the test:

=$ mkdir /var/tmp/test
=$ cd /var/tmp/test/
=$ export LD_LIBRARY_PATH=/opt/pgsql-8.3.11-int/lib/
=$ export PATH="/opt/pgsql-8.3.11-int/bin:$PATH"
=$ mkdir data-8.3
=$ initdb -D data-8.3
=$ pg_ctl -D data-8.3 -l logfile-8.3 start
=$ psql -d postgres -f /opt/pgsql-8.3.11-int/share/contrib/ltree.sql
=$ psql -d postgres -c "create table z (x ltree)"
=$ psql -d postgres -c "insert into z (x) values ('a.b')"
=$ pg_ctl -D data-8.3/ stop
=$ export LD_LIBRARY_PATH=/opt/pgsql-9.0.5a-int/lib/:/opt/pgsql-8.3.11-int/lib/
=$ export PATH=/opt/pgsql-9.0.5a-int/bin/:/opt/pgsql-8.3.11-int/bin/:~/bin:/usr/local/bin:/usr/bin:/bin
=$ mkdir data-9.0
=$ initdb -D data-9.0/
=$ perl -pi -e 's/#port = 5432/port=7654/' data-9.0/postgresql.conf
=$ pg_upgrade -v -b /opt/pgsql-8.3.11-int/bin/ -B /opt/pgsql-9.0.5a-int/bin/ -d $( pwd )/data-8.3/ -D $( pwd )/data-9.0 -k -l pg_upgrade.log -p 5432 -P 7654
=$ pg_ctl -D data-9.0 -l logfile-9.0 start
=$ psql -p 7654 -d postgres -c "select * from z"
WARNING: detected write past chunk end in ExecutorState 0xc500a0
WARNING: problem in alloc set ExecutorState: req size > alloc size for chunk 0xc500d8 in block 0xc4dfd0
WARNING: problem in alloc set ExecutorState: bad single-chunk 0xc500d8 in block 0xc4dfd0
WARNING: problem in alloc set ExecutorState: bogus aset link in block 0xc4dfd0, chunk 0xc500d8
WARNING: problem in alloc set ExecutorState: found inconsistent memory block 0xc4dfd0
connection to server was lost

Hope it helps.

Best regards,

depesz