BUG #6643: [PostgreSQL9.2beta1] COPY after changing fillfactor gets a PANIC.

The following bug has been logged on the website:

Bug reference:      6643
Logged by:          Tomonari Katsumata
Email address:      katsumata.tomonari@po.ntts.co.jp
PostgreSQL version: Unsupported/Unknown
Operating system:   RHEL 6.2 x86_64
Description:=20=20=20=20=20=20=20=20

Hi,

Now, I'm testing PostgreSQL 9.2 Beta 1.
And I have a problem.

Steps to procedure are bellow.

1. CREATE DATABASE
  export LANG=3DC
  initdb -D $PGDATA -E SQL_ASCII
  pg_ctl start
  createdb testdb

2. CREATE TABLE
  psql -d testdb -f ./create_table_customer.sql

3. ALTER TABLE(fillfactor)
  psql -d testdb -c "ALTER TABLE customer SET (fillfactor=3D90);"

4. LOAD DATA
  (please set correct path to customer.data)
  psql -d testdb -f ./customer.sql

Then, I have a PANIC error.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
BEGIN
TRUNCATE TABLE
PANIC:  failed to add tuple to page
CONTEXT:  COPY customer, line 296:
"296>ALNGAT>alngat>EgBEEAyXVIAWBE>KCiDDFsqA8Kv>2586068>4067234479>ALNGAT@ku=
vkaEEyi>20100905>20101023>..."
STATEMENT:  COPY customer FROM
'/home/katsumata/work/2012/20120516_PG92beta1_bug1/copy_panic_dbt1/copy_pan=
ic/customer.data'
WITH DELIMITER '>';
psql:./customer.sql:3: PANIC:  failed to add tuple to page
CONTEXT:  COPY customer, line 296:
"296>ALNGAT>alngat>EgBEEAyXVIAWBE>KCiDDFsqA8Kv>2586068>4067234479>ALNGAT@ku=
vkaEEyi>20100905>20101023>..."
PANIC:  failed to add tuple to page
CONTEXT:  COPY customer, line 296:
"296>ALNGAT>alngat>EgBEEAyXVIAWBE>KCiDDFsqA8Kv>2586068>4067234479>ALNGAT@ku=
vkaEEyi>20100905>20101023>..."
psql:./customer.sql:3: connection to server was lost
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

If I skip the 3rd step(ALTER TABLE(fillfactor)),
I don't have any ERROR.
And It's also OK on PostgreSQL 9.1.3.

Are there any changes about this behavior ?