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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Andrew Sullivan <ajs(at)commandprompt(dot)com>
- Cc: 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:27:02 -0400
- Message-id: <23351(dot)1211822822(at)sss(dot)pgh(dot)pa(dot)us>
Andrew Sullivan <ajs(at)commandprompt(dot)com> writes: > 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. I'm not so much wondering whether it will "work" as why it is segfaulting. regards, tom lane
- References:
- BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- From: Githogori Nyangara-Murage
- Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- From: Andrew Sullivan
- BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Prev by Date: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Next by Date: BUG #4200: Regexp character classes not UTF8-compliant
- Previous by thread: Re: BUG #4177: Dump and restore from Slonified 8.1.11 causes a segfault
- Next by thread: BUG #4179: pg_standby reports "file size greater than expected"
- Indexes: