Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: BUG #2781: database dump/restore problems
- From: "Thomas H." <me(at)alternize(dot)com>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: <pgsql-bugs(at)postgresql(dot)org>
- Subject: Re: BUG #2781: database dump/restore problems
- Date: Tue, 28 Nov 2006 13:34:45 +0100
regarding pg_dump: where there some changes from b3 to rc1 that wouldexplain the resulting rc1 pg_dump output (-c) being half as big as with b3?No... regards, tom lane
well, it was 300mb before rc1, and now its only 188mb. inbetween i did a vacuum full on one table. that shoulnd't affect backup size, should it? i'll restore one of the new backups later on to be sure all data is still there.
- thomas
- References:
- BUG #2781: database dump/restore problems
- From: Greg Peters
- Re: BUG #2781: database dump/restore problems
- From: Tom Lane
- Re: BUG #2781: database dump/restore problems
- From: Thomas H.
- Re: BUG #2781: database dump/restore problems
- From: Tom Lane
- BUG #2781: database dump/restore problems
- Prev by Date: BUG #2790: constructor for int2vector seems to be buggy
- Next by Date: BUG #2791: Error while commiting
- Previous by thread: Re: BUG #2781: database dump/restore problems
- Next by thread: BUG #2782: Too Many open files in system
- Indexes: