Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- From: Andrew Sullivan <ajs(at)commandprompt(dot)com>
- To: pgsql-bugs(at)postgresql(dot)org
- Subject: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Date: Mon, 26 May 2008 13:03:57 -0400
- Message-id: <20080526170356(dot)GB21327(at)commandprompt(dot)com>
On Sat, May 17, 2008 at 08:40:16AM +0000, Githogori Nyangara-Murage wrote: > > Either a pg_dumpall or pg_dump of a Slonified database on PostgreSQL 8.1.11 > causes a segfault When you say "slonified", do you mean "dumped from [some] replica [of at least one table]" or "dumped from origin"? If its the former, it will never work. A -- Andrew Sullivan ajs(at)commandprompt(dot)com +1 503 667 4564 x104 http://www.commandprompt.com/
- Follow-Ups:
- References:
- BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- From: Githogori Nyangara-Murage
- BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Prev by Date: Re: BUG #4196: Backend crash possible with psql
- Next by Date: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Previous by thread: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Next by thread: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Indexes: