Excerpts from Tom Lane's message of dom ago 15 22:54:31 -0400 2010: > I'm thinking that we need some sort of what-to-do-on-error flag passed > into RelationTruncate, plus at least order-of-operations fixes in > several other places, if not a wholesale refactoring of this whole call > stack. But I'm running out of steam and don't have a concrete proposal > to make right now. In any case, we've got more problems here than just > the original one of forgetting dirty buffers too soon.
I think this fell through the cracks. What are we going to do here? -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
