| From: | "Githogori Nyangara-Murage" <githogori(at)SiliconBazaar(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault |
| Date: | 2008-05-17 08:40:16 |
| Message-ID: | 200805170840.m4H8eG8i045893@wwwmaster.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 4177
Logged by: Githogori Nyangara-Murage
Email address: githogori(at)SiliconBazaar(dot)com
PostgreSQL version: 8.3.1
Operating system: CentOS 5.1
Description: Dump and restore from Slonified 8.1.11 causes a segfault
Details:
Either a pg_dumpall or pg_dump of a Slonified database on PostgreSQL 8.1.11
causes a segfault if I try to restore it on PostgreSQL 8.3.1. Got around it
by restoring onto another 8.1.11 and then did a cascaded drop <slony>
schema. The original Pg one was in production. The resulting dump was then
able to restore on an 8.3.1. Now we have 8.3.1 in production.
If you need more data, let me know since I can reproduce this at will.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reinhard Zitzmann | 2008-05-17 13:26:56 | BUG #4179: pg_standby reports "file size greater than expected" |
| Previous Message | Jaime Casanova | 2008-05-17 05:10:43 | wal_sync_method |