Sat Jun 30 06:09:58 PDT 2007
- Previous message: [Slony1-general] pg_dump, slony1_dump, sanity check
- Next message: [Slony1-general] pg_dump, slony1_dump, sanity check
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jun 29, 2007 at 03:25:00PM -0700, Bill Willits wrote: > > Can you explain if this is dependant on some version of PG or Slony? Or, PostgreSQL pg_dump prior to, I think, 8.1 (it might be 8.0) are not quite as aggressive in checking for some of these errors, so you don't get them when you dump the database. Unfortunately, you get garbage dumps. When you restore, you run a serious risk of running into problems you didn't know you could have. This is because the catalogue tables have been messed with by Slony. So, any database that has even _one_ replicated table in it (i.e. not the origin for every table) should never be dumped using pg_dump. A -- Andrew Sullivan | ajs at crankycanuck.ca When my information changes, I alter my conclusions. What do you do sir? --attr. John Maynard Keynes
- Previous message: [Slony1-general] pg_dump, slony1_dump, sanity check
- Next message: [Slony1-general] pg_dump, slony1_dump, sanity check
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list