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 <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-11-29 15:26:12|
|Subject: Re: Re: [COMMITTERS] pgsql: Remove outdated comments from
the regression test files.|
|Previous:||From: Alvaro Herrera||Date: 2010-11-29 13:30:36|
|Subject: Re: ToDo: enhanced diagnostic for plpgsql|
pgsql-bugs by date
|Next:||From: Mohammed Rashad||Date: 2010-11-29 15:02:46|
|Subject: postgresql-8.4 error|
|Previous:||From: Heikki Linnakangas||Date: 2010-11-29 13:53:18|
|Subject: Re: Migrated from TWS/WebAdmin 8.1 version to TWS/WebAdmin