On Thu, 5 Feb 2004, Tom Lane wrote: > "Marc G. Fournier" <[EMAIL PROTECTED]> writes: > > k, but that would be a different scenario, no? As I mentioned in my > > original, a DROP TABLE would reset its timeout to -1, meaning to close it > > and drop it on the next checkpoint interval ... > > How would it do that? These structs are local to particular backends, > so there's no way for a DROP TABLE occurring in one backend to reach > over and reset the timeout in the bgwriter process. If we add > communication that lets the bgwriter know the table is being dropped, > then the problem is solved directly.
D'oh, okay, took me a second to clue into what it was I wasn't cluing into ... got it now, thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
