Tom Lane wrote: > In CVS tip, try running the regression tests against an installed > postmaster (ie, make installcheck); then as soon as the tests are > done, kill -9 the bgwriter process to force a database restart. > Most of the time you'll get a PANIC during recovery:
[...] > This is impossible to fix nicely because the information to reconstruct > the tablespace is simply not available. We could make an ordinary > directory (not a symlink) under pg_tblspc and then limp along in the > expectation that it would get removed before we finish replay. Or we > could just skip logged operations on files within the tablespace, but > that feels pretty uncomfortable to me --- it amounts to deliberately > discarding data ... > > Any thoughts? How is a dropped table handled by the recovery code? Doesn't it present the same sort of issues (though on a smaller scale)? -- Kevin Brown [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
