Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> The correct use of dependency information would be to sort the DROPs > >> into an order that should succeed *without* CASCADE. (This will > >> actually happen for free AIUI, once pg_dump uses dependency info fully

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Bruce Momjian <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> The correct use of dependency information would be to sort the DROPs >> into an order that should succeed *without* CASCADE. (This will >> actually happen for free AIUI, once pg_dump uses dependency info fully. >> DROPping in the rever

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Once pg_dump starts using the dependency information, it seems it could > > do the drops in the proper order, and when it detects > > mutually-dependent tables, it can use a single DROP CASCADE to remove > > them all --- seems like tha

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Bruce Momjian <[EMAIL PROTECTED]> writes: > Once pg_dump starts using the dependency information, it seems it could > do the drops in the proper order, and when it detects > mutually-dependent tables, it can use a single DROP CASCADE to remove > them all --- seems like that is a TODO. You missed m

Re: [BUGS] True64 Unix v5.1 - postgresql-7.2.4 compilation problem

Not sure --- please try 7.3.4 or 7.4beta2. --- Karthik K S wrote: > > POSTGRESQL BUG REPORT TEMPLATE >

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Should we be using CASCADE? Seems that is going to double-drop some > > tables. > > It kinda scares me too. If you are loading into a database that already > has stuff in it, seems like CASCADE could lead to dropping stuff that is >

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

Bruce Momjian <[EMAIL PROTECTED]> writes: > Should we be using CASCADE? Seems that is going to double-drop some > tables. It kinda scares me too. If you are loading into a database that already has stuff in it, seems like CASCADE could lead to dropping stuff that is not part of the dataset being

Re: [BUGS] bug report: pg_dump does not use CASCADE in DROP

This is a tough one. The CASCADE shouldn't be needed because the clean should be done in an ordering so that dependency is honored. Of course, that doesn't fix problems with mutually-dependent tables. Should we be using CASCADE? Seems that is going to double-drop some tables.